From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans de Goede Subject: Re: [PATCH 2/8] mfd: axp20x: Add a cell for the usb power_supply part of the axp20x PMICs Date: Wed, 10 Jun 2015 09:57:13 +0200 Message-ID: <5577EDD9.8020900@redhat.com> References: <1433885881-19809-1-git-send-email-hdegoede@redhat.com> <1433885881-19809-3-git-send-email-hdegoede@redhat.com> Reply-To: hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , To: wens-jdAy2FN1RRM@public.gmane.org Cc: Lee Jones , Sebastian Reichel , Dmitry Eremin-Solenikov , David Woodhouse , Kishon Vijay Abraham I , Felipe Balbi , Maxime Ripard , =?UTF-8?B?QnJ1bm8gUHLDqW1vbnQ=?= , linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel , devicetree , linux-sunxi List-Id: devicetree@vger.kernel.org Hi, On 10-06-15 03:19, Chen-Yu Tsai wrote: > On Wed, Jun 10, 2015 at 5:37 AM, Hans de Goede wrot= e: >> Add a cell for the usb power_supply part of the axp20x PMICs. >> >> 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 separate= ly >> in devicetree as most boards do not use all 4. So in dt each one needs i= ts >> own child-node of the axp20x node. Another reason for using separate chi= ld >> 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. >> >> Cc: Bruno Pr=C3=A9mont >> Signed-off-by: Hans de Goede >> --- >> drivers/mfd/axp20x.c | 32 +++++++++++++++++++++++++++++++- >> 1 file changed, 31 insertions(+), 1 deletion(-) >> >> diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c >> index 6ffbc11..47ce233 100644 >> --- a/drivers/mfd/axp20x.c >> +++ b/drivers/mfd/axp20x.c >> @@ -113,6 +113,30 @@ static struct resource axp20x_pek_resources[] =3D { >> }, >> }; >> >> +static struct resource axp20x_usb_power_supply_resources[] =3D { >> + { >> + .name =3D "VBUS_PLUGIN", >> + .start =3D AXP20X_IRQ_VBUS_PLUGIN, >> + .end =3D AXP20X_IRQ_VBUS_PLUGIN, >> + .flags =3D IORESOURCE_IRQ, >> + }, { >> + .name =3D "VBUS_REMOVAL", >> + .start =3D AXP20X_IRQ_VBUS_REMOVAL, >> + .end =3D AXP20X_IRQ_VBUS_REMOVAL, >> + .flags =3D IORESOURCE_IRQ, >> + }, { >> + .name =3D "VBUS_VALID", >> + .start =3D AXP20X_IRQ_VBUS_VALID, >> + .end =3D AXP20X_IRQ_VBUS_VALID, >> + .flags =3D IORESOURCE_IRQ, >> + }, { >> + .name =3D "VBUS_NOT_VALID", >> + .start =3D AXP20X_IRQ_VBUS_NOT_VALID, >> + .end =3D AXP20X_IRQ_VBUS_NOT_VALID, >> + .flags =3D IORESOURCE_IRQ, >> + }, >> +}; >> + >> static struct resource axp22x_pek_resources[] =3D { >> { >> .name =3D "PEK_DBR", >> @@ -165,7 +189,7 @@ static const struct regmap_config axp20x_regmap_conf= ig =3D { >> .val_bits =3D 8, >> .wr_table =3D &axp20x_writeable_table, >> .volatile_table =3D &axp20x_volatile_table, >> - .max_register =3D AXP20X_FG_RES, >> + .max_register =3D AXP20X_OCV(15), >> .cache_type =3D REGCACHE_RBTREE, >> }; >> >> @@ -368,6 +392,12 @@ static struct mfd_cell axp20x_cells[] =3D { >> .resources =3D axp20x_pek_resources, >> }, { >> .name =3D "axp20x-regulator", >> + }, { >> + .name =3D "axp20x-usb-power-supply", > > Could we use either "vbus-power-supply" to match the AXP datasheets, > or "otg-power-supply" which is slightly more obvious to board owners? I do not like the vbus name, since it does not indicate which bus it is, OTOH you are right that is what it is called in the datasheet. As for using otg, I think that usb is better then. All in all I believe that the current usb name is best, but if others disagree I'm open to renaming this. So anyone else have an opinion on what would be a good name for the cell and the compatible ? Regards, Hans --=20 You received this message because you are subscribed to the Google Groups "= linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to linux-sunxi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit https://groups.google.com/d/optout.