[RFC v3 08/13] ahci-platform: Allow specifying platform_data through of_device_id
Hans de Goede
hdegoede at redhat.com
Sun Jan 19 13:56:53 EST 2014
Hi,
On 01/19/2014 12:38 PM, Tejun Heo wrote:
> On Sun, Jan 19, 2014 at 12:48:50AM +0100, Hans de Goede wrote:
>> @@ -126,7 +151,7 @@ static void ahci_put_clks(struct ahci_host_priv *hpriv)
>> static int ahci_probe(struct platform_device *pdev)
>> {
>> struct device *dev = &pdev->dev;
>> - struct ahci_platform_data *pdata = dev_get_platdata(dev);
>> + const struct ahci_platform_data *pdata = ahci_get_pdata(dev);
>
> Let's please not add const. For data types which are known to be
> terminal, const more or less works, I suppose but for anything even
> mildly complicated it ends up being more of a headache. C just
> doesn't have enough language support to make const actually useful.
> e.g. now if somebody wants to add an accessor to ahci_platform_data()
> which is applicable to both readers and writers, we either need two
> separate accessors for const and !const paths or have to cast away
> const.
The problem is that:
1) of_match_device returns const, so without the const the code would need
to cast that const away somewhere
2) of_match_device is right to return const because
2a) the data can actually be const
2b) even if not const, it is shared between multiple instances of the same
device-type and thus should never be written too
So as Russell already said, the use of const is correct here, and the best
thing to do is to simply keep it.
Regards,
Hans
More information about the linux-arm-kernel
mailing list