[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57289E35.8040400@nvidia.com>
Date: Tue, 3 May 2016 18:18:53 +0530
From: Laxman Dewangan <ldewangan@...dia.com>
To: Jon Hunter <jonathanh@...dia.com>, <swarren@...dotorg.org>,
<linus.walleij@...aro.org>, <gnurou@...il.com>,
<robh+dt@...nel.org>, <mark.rutland@....com>,
<thierry.reding@...il.com>
CC: <linux-tegra@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-gpio@...r.kernel.org>
Subject: Re: [PATCH 3/6] soc/tegra: pmc: Add support for IO pads power state
and voltage
On Tuesday 03 May 2016 06:25 PM, Jon Hunter wrote:
>
>>
>> Currently SOR driver is using the tegra_io_rail_power_off/on() APIs.
>> Once the proper interface available then I will move sor driver to use
>> new method and then we can full get rid of older APIs and macros.
>>
>> Till that, we need to have this.
> I prefer it is done before this series. In other words, if we need a
> proper enum for the rail/pad IDs then add one and convert any existing
> drivers over to use any new APIs first.
But the converting to new API can be done after this patch only.
I need to implement new APIs and then move driver to use new APIs and
then remove older one.
Otherwise, I need to have single patch for the new API + converting
existing user to use new APIs.
If this is allowed in subsystem level then this is best method.
We already did for max77686 RTC + mfd change together.
So will it be fine to make such changes?
Powered by blists - more mailing lists