From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: lee.jones@linaro.org, cw00.choi@samsung.com,
myungjoo.ham@samsung.com, lgirdwood@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH v2 2/3] regulator: arizona: Add regulator specific device tree binding document
Date: Thu, 22 Oct 2015 13:44:49 +0100 [thread overview]
Message-ID: <20151022124449.GH8232@sirena.org.uk> (raw)
In-Reply-To: <1444916828-8965-2-git-send-email-ckeepax@opensource.wolfsonmicro.com>
[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]
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.
> +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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-10-22 23:34 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
2015-10-22 12:44 ` Mark Brown [this message]
2015-10-26 11:28 ` Charles Keepax
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=20151022124449.GH8232@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=patches@opensource.wolfsonmicro.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