From: Charles Keepax <ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
cw00.choi-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
myungjoo.ham-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
patches-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org
Subject: Re: [PATCH v2 2/3] regulator: arizona: Add regulator specific device tree binding document
Date: Mon, 26 Oct 2015 11:28:20 +0000 [thread overview]
Message-ID: <20151026112820.GI10520@ck-lbox> (raw)
In-Reply-To: <20151022124449.GH8232-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On Thu, Oct 22, 2015 at 01:44:49PM +0100, Mark Brown wrote:
> On Thu, Oct 15, 2015 at 02:47:07PM +0100, Charles Keepax wrote:
>
> > +This document lists regulator specific bindings, see the primary binding
> > +document:
> > + ../mfd/arizona.txt
> > +
> > +Required properties:
> > +
> > + - AVDD-supply, DBVDD1-supply, CPVDD-supply : Power supplies for the device,
> > + as covered in regulator.txt
> > +
> > + - DBVDD2-supply, DBVDD3-supply : Additional databus power supplies (wm5102,
> > + wm5110, wm8280, wm8998, wm1814)
> > +
> > + - SPKVDDL-supply, SPKVDDR-supply : Speaker driver power supplies (wm5102,
> > + wm5110, wm8280, wm8998, wm1814)
> > +
> > + - SPKVDD-supply : Speaker driver power supply (wm8997)
> > +
>
> I'd expect these to be on the MFD since they're (with the exception of
> AVDD which supplies the regulators IIRC) not part of the regulator
> component of the device and are core for bringing it online.
Yeah, fair enough I will move those back into the MFD part.
>
> > +Optional properties:
> > + - wlf,ldoena : GPIO specifier for the GPIO controlling LDOENA
> > +
> > +Optional subnodes:
> > + - ldo1 : Initial data for the LDO1 regulator, as covered in
> > + Documentation/devicetree/bindings/regulator/regulator.txt
> > + - micvdd : Initial data for the MICVDD regulator, as covered in
> > + Documentation/devicetree/bindings/regulator/regulator.txt
>
> These are the properties for the regulator itself.
>
> > +++ b/MAINTAINERS
> > @@ -11381,6 +11381,7 @@ W: http://opensource.wolfsonmicro.com/content/linux-drivers-wolfson-devices
> > S: Supported
> > F: Documentation/hwmon/wm83??
> > F: Documentation/devicetree/bindings/extcon/extcon-arizona.txt
> > +F: Documentation/devicetree/bindings/regulator/arizona-regulator.txt
> > F: arch/arm/mach-s3c64xx/mach-crag6410*
> > F: drivers/clk/clk-wm83*.c
> > F: drivers/extcon/extcon-arizona.c
>
> I'd suggest moving this to a separate patch which adds all the new files
> together to make it easier to merge things.
Yeah no problem with making that a seperate patch.
Thanks,
Charles
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-10-26 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 13:47 [PATCH v2 1/3] extcon: arizona: Add extcon specific device tree binding document Charles Keepax
2015-10-15 13:47 ` [PATCH v2 2/3] regulator: arizona: Add regulator " Charles Keepax
[not found] ` <1444916828-8965-2-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2015-10-22 12:44 ` Mark Brown
[not found] ` <20151022124449.GH8232-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-10-26 11:28 ` Charles Keepax [this message]
[not found] ` <1444916828-8965-1-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2015-10-15 13:47 ` [PATCH v2 3/3] mfd: arizona: Remove bindings covered in new subsystem specific docs Charles Keepax
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=20151026112820.GI10520@ck-lbox \
--to=ckeepax-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=cw00.choi-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=myungjoo.ham-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=patches-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.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).