From: Keerthy <a0393675@ti.com>
To: Nishanth Menon <nm@ti.com>, Mark Brown <broonie@kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>
Cc: Tony Lindgren <tony@atomide.com>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>, Liam Girdwood <lgirdwood@gmail.com>,
Keerthy <j-keerthy@ti.com>, Stephen Warren <swarren@nvidia.com>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH 0/4] regulator: tps65917/palmas: Cleanups and bugfixes
Date: Fri, 20 May 2016 10:01:02 +0530 [thread overview]
Message-ID: <573E9306.5050908@ti.com> (raw)
In-Reply-To: <572CEA22.2090300@ti.com>
+ Lee Jones
On Saturday 07 May 2016 12:31 AM, Nishanth Menon wrote:
> On 05/06/2016 12:14 PM, Mark Brown wrote:
>> On Fri, May 06, 2016 at 12:44:23PM +0530, Laxman Dewangan wrote:
>>
>>> When you are here, can you implement the dt parsing with the new method from
>>> regulator framework.
>>> Regulator FW calls callback to parse customized DT property, just need to
>>> pass the node and pointer when registering.
>>
>>> This will helps lots in cleanups and readability.
>>
>> Yes, please.
>>
> yeah, the driver has started showing it's age, it will be good to do a
> refactor.
Laxman,
I got the dt parsing with new method from regulator framework part, But
by new method do you also want to remove the dt compatible of regulators
and let only the mfd compatible stay?
replace of_platform_populate with mfd_add_devices so that linux handles
the drivers split up and not the device tree?
Regards,
Keerthy
>
next prev parent reply other threads:[~2016-05-20 4:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 0:29 [PATCH 0/4] regulator: tps65917/palmas: Cleanups and bugfixes Nishanth Menon
2016-05-06 0:29 ` [PATCH 1/4] regulator: tps65917/palmas: Simplify multiple dereference of ddata->palmas_matches[idx] Nishanth Menon
2016-05-06 17:19 ` Applied "regulator: tps65917/palmas: Simplify multiple dereference of ddata->palmas_matches[idx]" to the regulator tree Mark Brown
2016-05-06 0:29 ` [PATCH 2/4] regulator: tps65917/palmas: Simplify multiple dereference of pdata->reg_init[idx] Nishanth Menon
2016-05-06 17:18 ` Applied "regulator: tps65917/palmas: Simplify multiple dereference of pdata->reg_init[idx]" to the regulator tree Mark Brown
2016-05-06 0:29 ` [PATCH 3/4] regulator: tps65917/palmas: Handle possible memory allocation failure Nishanth Menon
2016-05-06 17:18 ` Applied "regulator: tps65917/palmas: Handle possible memory allocation failure" to the regulator tree Mark Brown
2016-05-06 0:29 ` [PATCH 4/4] regulator: tps65917/palmas: Simplify multiple dereference of match->of_node Nishanth Menon
2016-05-06 17:18 ` Applied "regulator: tps65917/palmas: Simplify multiple dereference of match->of_node" to the regulator tree Mark Brown
2016-05-06 7:14 ` [PATCH 0/4] regulator: tps65917/palmas: Cleanups and bugfixes Laxman Dewangan
2016-05-06 17:14 ` Mark Brown
2016-05-06 19:01 ` Nishanth Menon
2016-05-20 4:31 ` Keerthy [this message]
2016-05-20 6:16 ` Laxman Dewangan
2016-07-08 5:28 ` Keerthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=573E9306.5050908@ti.com \
--to=a0393675@ti.com \
--cc=broonie@kernel.org \
--cc=j-keerthy@ti.com \
--cc=ldewangan@nvidia.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=swarren@nvidia.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).