[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <76797622-733f-fe00-4a15-46a5f867a186@ti.com>
Date: Mon, 12 Feb 2018 13:32:20 +0530
From: Kishon Vijay Abraham I <kishon@...com>
To: Sekhar Nori <nsekhar@...com>, David Lechner <david@...hnology.com>,
<linux-arm-kernel@...ts.infradead.org>
CC: Kevin Hilman <khilman@...nel.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Adam Ford <aford173@...il.com>, <linux-kernel@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>, Lee Jones <lee.jones@...aro.org>
Subject: Re: [PATCH] ARM: da8xx: use platform data for CFGCHIP syscon regmap
On Monday 12 February 2018 01:26 PM, Sekhar Nori wrote:
> On Thursday 25 January 2018 08:57 PM, Sekhar Nori wrote:
>> + Arnd, Kishon and Lee for their information.
>>
>> On Wednesday 24 January 2018 05:06 AM, David Lechner wrote:
>>> This converts from using a platform device for the CFGCHIP syscon
>>> regmap to using platform data to pass the regmap to consumers.
>>>
>>> A lazy getter function is used so that the regmap will only be
>>> created if it is actually used. This function will also be used
>>> in the clock init when we convert to the common clock framework.
>>>
>>> The USB PHY driver is currently the only consumer. This driver is
>>> updated to use platform data to get the CFGCHIP regmap instead of
>>> syscon_regmap_lookup_by_pdevname().
>>>
>>> Signed-off-by: David Lechner <david@...hnology.com>
>>> ---
>>>
>>> This is based on the feedback from the series "ARM: davinci: common clock prep
>>> work". https://lkml.org/lkml/2018/1/19/715
>>
>> It will be nice to have the discussion link as part of commit description.
>>
>> Links:
>> https://lkml.kernel.org/r/<CAK8P3a1AP1sz3nT8S6WMupo3iSVRsn2t9sPg2Mj1RAY1AS58UQ@...l.gmail.com>
>>
>> Kishon,
>>
>> With your ack I would like to queue this through the DaVinci tree for
>
> Kishon, ping on this.
Acked-by: Kishon Vijay Abraham I <kishon@...com>
>
>> v4.17. Due to ongoing common clock framework conversion effort, I expect
>> to queue a number of other patches dependent on this.
>>
>> Once v4.16-rc1 comes out, I can provide an immutable commit/tag with
>> just this patch applied. You can use that if you end up queuing other
>> patches which conflict with this.
>>
>> Let me know.
>
> Thanks,
> Sekhar
>
Powered by blists - more mailing lists