From: Mark Brown <broonie@kernel.org>
To: Andrei.Stefanescu@microchip.com
Cc: lgirdwood@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com,
gregkh@linuxfoundation.org, Nicolas.Ferre@microchip.com,
Cristian.Birsan@microchip.com, Claudiu.Beznea@microchip.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] regulator: dt-bindings: add MCP16502 regulator bindings
Date: Tue, 13 Nov 2018 09:30:37 -0800 [thread overview]
Message-ID: <20181113173036.GA2089@sirena.org.uk> (raw)
In-Reply-To: <1542108563-10108-2-git-send-email-andrei.stefanescu@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
On Tue, Nov 13, 2018 at 11:29:24AM +0000, Andrei.Stefanescu@microchip.com wrote:
> +- lpm-gpio: GPIO for LPM pin. Note that this GPIO *must* remain high during
> + suspend-to-ram, keeping the PMIC into HIBERNATE mode.
All GPIO properties should be -gpios even if they can only ever have one
GPIO.
> +- regulators: A node that houses a sub-node for each regulator within
> + the device. Each sub-node is identified using the node's
> + name. The content of each sub-node is defined by the
> + standard binding for regulators; see regulator.txt.
You should describe which regulators exist for the device.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-11-13 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 11:29 [PATCH 0/3] add support for MCP16502 PMIC Andrei.Stefanescu
2018-11-13 11:29 ` [PATCH 1/3] regulator: dt-bindings: add MCP16502 regulator bindings Andrei.Stefanescu
2018-11-13 17:30 ` Mark Brown [this message]
2018-11-13 11:29 ` [PATCH 2/3] MAINTAINERS: add maintainer for MCP16502 PMIC driver Andrei.Stefanescu
2018-11-13 11:29 ` [PATCH 3/3] regulator: mcp16502: add regulator driver for MCP16502 Andrei.Stefanescu
2018-11-13 17:45 ` Mark Brown
2018-11-21 15:44 ` Andrei.Stefanescu
2018-11-23 13:44 ` Mark Brown
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=20181113173036.GA2089@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Andrei.Stefanescu@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Cristian.Birsan@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®