From: "Andrew F. Davis" <afd@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Lee Jones <lee.jones@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/5] regulators: tps65912: Add regulator driver for the TPS65912 PMIC
Date: Tue, 29 Sep 2015 13:08:50 -0500 [thread overview]
Message-ID: <560AD3B2.1070102@ti.com> (raw)
In-Reply-To: <20150929151320.GT30445@sirena.org.uk>
On 09/29/2015 10:13 AM, Mark Brown wrote:
> On Fri, Sep 25, 2015 at 03:10:04PM -0500, Andrew F. Davis wrote:
>> On 09/25/2015 01:05 PM, Mark Brown wrote:
>>> On Thu, Sep 24, 2015 at 09:52:53AM -0500, Andrew F. Davis wrote:
>
>>>> + match = of_match_device(tps65912_regulator_of_match_table, &pdev->dev);
>>>> + if (!match)
>>>> + return -ENODEV;
>
>>>> + template = match->data;
>>>> + id = template->id;
>>>> + init_data = of_get_regulator_init_data(&pdev->dev, pdev->dev.of_node,
>>>> + ®ulators[id]);
>
>>> Don't open code this stuff, use the core DT matching in the
>>> regulator_desc instead.
>
>> I assume you are referring to your additions in a0c7b164ad11? If so I'm not
>
> Please don't refer to commits by ID only, include a human readable
> description of the commit for the benefit of any humans who might read
> your mail.
>
Forgot about those pesky humans :), OK, will do from now on.
>> sure that will save me anything as my probe function is called with a DT
>> match already, so no searching is needed.
>
> You've not understood what that change is replacing, the code I'm
> quoting above is exactly that code. Check out some of the existing
> drivers using this API.
>
Looking at other drivers that use this API they all call regulator_register
in a loop in their probe, once for each possible regulator, in this case
letting the API do the DT node search makes sense. My probe on the other-hand
is only called when we already have a DT match, therefor searching is not
necessary and all I have to do is call of_get_regulator_init_data myself on
the already found DT node. No need to add node names to my regulator_desc
and make the API re-search for the node.
I have further cleaned up this code to show this.
If this is acceptable, I'll push the re-spin so you can review further.
>>> Please also use subject lines mathcing the style for the subsystem.
>
>> I'm not sure I know what you mean? What is wrong with my subject line, it looks
>> like the others I've looked at?
>
> You are using "regulators:", the regulator API uses "regulator:" - this
> should be really clear if you do something like a git shortlog.
>
Ah, slipped right past me, thanks for clarifying, fixed.
WARNING: multiple messages have this Message-ID (diff)
From: "Andrew F. Davis" <afd@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Lee Jones <lee.jones@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 4/5] regulators: tps65912: Add regulator driver for the TPS65912 PMIC
Date: Tue, 29 Sep 2015 13:08:50 -0500 [thread overview]
Message-ID: <560AD3B2.1070102@ti.com> (raw)
In-Reply-To: <20150929151320.GT30445@sirena.org.uk>
On 09/29/2015 10:13 AM, Mark Brown wrote:
> On Fri, Sep 25, 2015 at 03:10:04PM -0500, Andrew F. Davis wrote:
>> On 09/25/2015 01:05 PM, Mark Brown wrote:
>>> On Thu, Sep 24, 2015 at 09:52:53AM -0500, Andrew F. Davis wrote:
>
>>>> + match = of_match_device(tps65912_regulator_of_match_table, &pdev->dev);
>>>> + if (!match)
>>>> + return -ENODEV;
>
>>>> + template = match->data;
>>>> + id = template->id;
>>>> + init_data = of_get_regulator_init_data(&pdev->dev, pdev->dev.of_node,
>>>> + ®ulators[id]);
>
>>> Don't open code this stuff, use the core DT matching in the
>>> regulator_desc instead.
>
>> I assume you are referring to your additions in a0c7b164ad11? If so I'm not
>
> Please don't refer to commits by ID only, include a human readable
> description of the commit for the benefit of any humans who might read
> your mail.
>
Forgot about those pesky humans :), OK, will do from now on.
>> sure that will save me anything as my probe function is called with a DT
>> match already, so no searching is needed.
>
> You've not understood what that change is replacing, the code I'm
> quoting above is exactly that code. Check out some of the existing
> drivers using this API.
>
Looking at other drivers that use this API they all call regulator_register
in a loop in their probe, once for each possible regulator, in this case
letting the API do the DT node search makes sense. My probe on the other-hand
is only called when we already have a DT match, therefor searching is not
necessary and all I have to do is call of_get_regulator_init_data myself on
the already found DT node. No need to add node names to my regulator_desc
and make the API re-search for the node.
I have further cleaned up this code to show this.
If this is acceptable, I'll push the re-spin so you can review further.
>>> Please also use subject lines mathcing the style for the subsystem.
>
>> I'm not sure I know what you mean? What is wrong with my subject line, it looks
>> like the others I've looked at?
>
> You are using "regulators:", the regulator API uses "regulator:" - this
> should be really clear if you do something like a git shortlog.
>
Ah, slipped right past me, thanks for clarifying, fixed.
next prev parent reply other threads:[~2015-09-29 18:09 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 14:52 [PATCH v3 0/5] mfd: tps65912: Driver rewrite with DT support Andrew F. Davis
2015-09-24 14:52 ` Andrew F. Davis
2015-09-24 14:52 ` [PATCH v3 1/5] Documentation: tps65912: Add DT bindings for the TPS65912 PMIC Andrew F. Davis
2015-09-24 14:52 ` Andrew F. Davis
2015-10-02 11:12 ` Linus Walleij
2015-09-24 14:52 ` [PATCH v3 2/5] mfd: tps65912: Remove old driver in preparation for new driver Andrew F. Davis
2015-09-24 14:52 ` Andrew F. Davis
[not found] ` <1443106374-4126-3-git-send-email-afd-l0cyMroinI0@public.gmane.org>
2015-09-25 16:52 ` Lee Jones
2015-09-25 16:52 ` Lee Jones
2015-10-02 12:16 ` Linus Walleij
2015-09-24 14:52 ` [PATCH v3 3/5] mfd: tps65912: Add driver for the TPS65912 PMIC Andrew F. Davis
2015-09-24 14:52 ` Andrew F. Davis
[not found] ` <1443106374-4126-4-git-send-email-afd-l0cyMroinI0@public.gmane.org>
2015-09-25 16:50 ` Lee Jones
2015-09-25 16:50 ` Lee Jones
2015-09-25 19:13 ` Andrew F. Davis
2015-09-25 19:13 ` Andrew F. Davis
[not found] ` <56059CDA.4020004-l0cyMroinI0@public.gmane.org>
2015-09-25 21:24 ` Lee Jones
2015-09-25 21:24 ` Lee Jones
2015-09-28 15:43 ` Andrew F. Davis
2015-09-28 15:43 ` Andrew F. Davis
2015-09-29 7:19 ` Lee Jones
2015-09-29 15:50 ` Andrew F. Davis
2015-09-29 15:50 ` Andrew F. Davis
2015-09-28 16:01 ` Grygorii Strashko
2015-09-28 16:01 ` Grygorii Strashko
2015-09-29 18:16 ` Andrew F. Davis
2015-09-29 18:16 ` Andrew F. Davis
2015-09-24 14:52 ` [PATCH v3 4/5] regulators: tps65912: Add regulator " Andrew F. Davis
2015-09-24 14:52 ` Andrew F. Davis
[not found] ` <1443106374-4126-5-git-send-email-afd-l0cyMroinI0@public.gmane.org>
2015-09-25 18:05 ` Mark Brown
2015-09-25 18:05 ` Mark Brown
2015-09-25 20:10 ` Andrew F. Davis
2015-09-25 20:10 ` Andrew F. Davis
2015-09-29 15:13 ` Mark Brown
2015-09-29 18:08 ` Andrew F. Davis [this message]
2015-09-29 18:08 ` Andrew F. Davis
2015-09-29 18:38 ` Mark Brown
2015-09-29 18:58 ` Andrew F. Davis
2015-09-29 18:58 ` Andrew F. Davis
2015-09-30 17:28 ` Mark Brown
2015-09-30 20:29 ` Andrew F. Davis
2015-09-30 20:29 ` Andrew F. Davis
2015-09-30 22:20 ` Mark Brown
2015-09-30 23:32 ` Andrew F. Davis
2015-09-30 23:32 ` Andrew F. Davis
2015-10-01 10:53 ` Mark Brown
2015-10-01 15:33 ` Grygorii Strashko
2015-10-01 15:33 ` Grygorii Strashko
2015-10-01 16:08 ` Andrew F. Davis
2015-10-01 16:08 ` Andrew F. Davis
2015-10-01 16:25 ` Mark Brown
2015-09-24 14:52 ` [PATCH v3 5/5] gpio: tps65912: Add GPIO " Andrew F. Davis
2015-09-24 14:52 ` Andrew F. Davis
2015-09-28 2:54 ` Alexandre Courbot
[not found] ` <CAAVeFuKu8R5GCQo3NySCOVLUew4_1qpYydHPAz9tfNorj27-NA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-28 15:52 ` Andrew F. Davis
2015-09-28 15:52 ` Andrew F. Davis
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=560AD3B2.1070102@ti.com \
--to=afd@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sameo@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.