From: Hans de Goede <hdegoede@redhat.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: "Sebastian Reichel" <sre@kernel.org>,
"Dmitry Eremin-Solenikov" <dbaryshkov@gmail.com>,
"David Woodhouse" <dwmw2@infradead.org>,
"Maxime Ripard" <maxime.ripard@free-electrons.com>,
"Bruno Prémont" <bonbons@linux-vserver.org>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree <devicetree@vger.kernel.org>,
linux-sunxi@googlegroups.com
Subject: Re: [linux-sunxi] Re: [PATCH v2 3/4] mfd: axp20x: Add a cell for the usb power_supply part of the axp20x PMICs
Date: Wed, 24 Jun 2015 17:04:28 +0200 [thread overview]
Message-ID: <558AC6FC.1050603@redhat.com> (raw)
In-Reply-To: <20150624112333.GH15013@x1>
Hi,
On 24-06-15 13:23, Lee Jones wrote:
>> Add a cell for the usb power_supply part of the axp20x PMICs.
>
> Why are you duplicating the subject line?
Heh, because some maintainers insist that the main-body part of the
commit message must stand by itself, without needing the subject to be
understandable...
>> Note that this cell is only for the usb power_supply part and not the
>> ac-power / battery-charger / rtc-backup-bat-charger bits.
>>
>> Depending on the board each of those must be enabled / disabled separately
>> in devicetree as most boards do not use all 4. So in dt each one needs its
>> own child-node of the axp20x node. Another reason for using separate child
>> nodes for each is so that other devicetree nodes can have a power-supply
>> property with a phandle referencing a node representing a single
>> power-supply.
>>
>> The decision to use a separate devicetree node for each is reflected on
>> the kernel side by each getting its own mfd-cell / platform_device and
>> platform-driver.
>
> You don't really need to say any of this, as this is the 'norm'.
I agree it should be the norm, but I'm not sure if it actually is, while
working on this I've seen several drivers which instantiate multiple
power-supply class devices from a single mfd-cell. And this is what
Bruno's original patches did, so I would prefer to keep this
> What you didn't mention however, is that you're taking the opportunity
> to fix some formatting issues and that there are no functional changes
> in these lines.
That is the end result of your request to change the indentation to
avoid line-wrapping :)
>
>> Cc: Bruno Prémont <bonbons@linux-vserver.org>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>> Changes in v2:
>> -Use DEFINE_RES_IRQ_NAMED
>> -Change indentation of axp20x_cells initializers to avoid line wrapping
>> ---
>> drivers/mfd/axp20x.c | 20 ++++++++++++++++----
>> 1 file changed, 16 insertions(+), 4 deletions(-)
>
> Patch looks okay however:
>
> Acked-by: Lee Jones <lee.jones@linaro.org>
Thanks.
Regards,
Hans
>
>> diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c
>> index f9a3c2d..ca4a604 100644
>> --- a/drivers/mfd/axp20x.c
>> +++ b/drivers/mfd/axp20x.c
>> @@ -113,6 +113,13 @@ static struct resource axp20x_pek_resources[] = {
>> },
>> };
>>
>> +static struct resource axp20x_usb_power_supply_resources[] = {
>> + DEFINE_RES_IRQ_NAMED(AXP20X_IRQ_VBUS_PLUGIN, "VBUS_PLUGIN"),
>> + DEFINE_RES_IRQ_NAMED(AXP20X_IRQ_VBUS_REMOVAL, "VBUS_REMOVAL"),
>> + DEFINE_RES_IRQ_NAMED(AXP20X_IRQ_VBUS_VALID, "VBUS_VALID"),
>> + DEFINE_RES_IRQ_NAMED(AXP20X_IRQ_VBUS_NOT_VALID, "VBUS_NOT_VALID"),
>> +};
>> +
>> static struct resource axp22x_pek_resources[] = {
>> {
>> .name = "PEK_DBR",
>> @@ -363,11 +370,16 @@ static const struct regmap_irq_chip axp288_regmap_irq_chip = {
>>
>> static struct mfd_cell axp20x_cells[] = {
>> {
>> - .name = "axp20x-pek",
>> - .num_resources = ARRAY_SIZE(axp20x_pek_resources),
>> - .resources = axp20x_pek_resources,
>> + .name = "axp20x-pek",
>> + .num_resources = ARRAY_SIZE(axp20x_pek_resources),
>> + .resources = axp20x_pek_resources,
>> }, {
>> - .name = "axp20x-regulator",
>> + .name = "axp20x-regulator",
>> + }, {
>> + .name = "axp20x-usb-power-supply",
>> + .of_compatible = "x-powers,axp202-usb-power-supply",
>> + .num_resources = ARRAY_SIZE(axp20x_usb_power_supply_resources),
>> + .resources = axp20x_usb_power_supply_resources,
>> },
>> };
>>
>
next prev parent reply other threads:[~2015-06-24 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 16:09 [PATCH v2 0/4] mfd/power: axp20x-usb-power driver Hans de Goede
[not found] ` <1434211748-25572-1-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-06-13 16:09 ` [PATCH v2 1/4] ARM: dts: Add binding documentation for AXP20x pmic usb power supply Hans de Goede
2015-06-13 16:09 ` [PATCH v2 2/4] mfd: axp20x: Add missing registers, and mark more registers volatile Hans de Goede
[not found] ` <1434211748-25572-3-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-06-24 11:19 ` Lee Jones
2015-06-13 16:09 ` [PATCH v2 3/4] mfd: axp20x: Add a cell for the usb power_supply part of the axp20x PMICs Hans de Goede
[not found] ` <1434211748-25572-4-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-06-24 11:23 ` Lee Jones
2015-06-24 15:04 ` Hans de Goede [this message]
[not found] ` <558AC6FC.1050603-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-06-25 8:51 ` Lee Jones
2015-06-13 16:09 ` [PATCH v2 4/4] power: Add an axp20x-usb-power driver Hans de Goede
[not found] ` <1434211748-25572-5-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-06-24 11:25 ` Lee Jones
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=558AC6FC.1050603@redhat.com \
--to=hdegoede@redhat.com \
--cc=bonbons@linux-vserver.org \
--cc=dbaryshkov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@free-electrons.com \
--cc=sre@kernel.org \
/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).