[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <942893991cc34410bf1515a6a970c5c2@svr-chch-ex1.atlnz.lc>
Date: Sun, 2 Jul 2017 21:51:44 +0000
From: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To: Andy Shevchenko <andy.shevchenko@...il.com>,
Wolfram Sang <wsa@...-dreams.de>
CC: linux-i2c <linux-i2c@...r.kernel.org>,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Linux-SH <linux-sh@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 5/6] i2c: pca-platform: use device_property_read_u32
On 30/06/17 22:56, Andy Shevchenko wrote:
> On Fri, Jun 30, 2017 at 12:03 PM, Wolfram Sang <wsa@...-dreams.de> wrote:
>>
>>>> - i2c->algo_data.i2c_clock = 59000;
>>>> + ret = device_property_read_u32(&pdev->dev, "clock-frequency",
>>>> + &i2c->algo_data.i2c_clock);
>>>> + if (ret)
>>>> + i2c->algo_data.i2c_clock = 59000;
>>>
>>> My idea is to get rid of legacy platform data completely.
>>> That's why I suggested device_* in the first place.
>>>
>>> In similar way like you did with GPIO lookup table, you may use
>>> PROPERTY_ENTRY*() macros in the board files.
>>>
>>> Does it make sense?
>>
>> Frankly, I am not a big fan of converting board files if we cannot test
>> the changes.
>
> So, if no one is using that old boards, should we really take care
> more than just compile test?
>
> P.S. Legacy platform data makes a burden of development nowadays.
> Built-in device properties API (as a part of Unified Device
> Properties) is exactly for getting rid of legacy stuff and make things
> much cleaner.
We could probably go with an approach of making the device properties
the default which would suit the new style and leave the platform_data
to override things if it is present.
If/when the older platforms go away we can drop struct
i2c_pca9564_pf_platform_data.
Powered by blists - more mailing lists