From: Rob Herring <robh@kernel.org>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: devicetree@vger.kernel.org, linux-power@fi.rohmeurope.com,
Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org,
mazziesaccount@gmail.com, Rob Herring <robh+dt@kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Wim Van Sebroeck <wim@linux-watchdog.org>
Subject: Re: [PATCH v3 1/4] dt_bindings: mfd: Add ROHM BD9576MUF and BD9573MUF PMICs
Date: Tue, 29 Sep 2020 09:53:19 -0500 [thread overview]
Message-ID: <20200929145319.GA575227@bogus> (raw)
In-Reply-To: <be3518afb2a54ff02ca15e63cac21c99bcdfaef6.1601366711.git.matti.vaittinen@fi.rohmeurope.com>
On Tue, 29 Sep 2020 11:15:31 +0300, Matti Vaittinen wrote:
> Add bindings for ROHM BD9576MUF and BD9573MUF PMICs. These
> PMICs are primarily intended to be used to power the R-Car series
> processors. They provide 6 power outputs, safety features and a
> watchdog with two functional modes.
>
> Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
> ---
>
> Changes from v2:
> - Replace bindings hw_margin_ms and rohm,hw-margin-min-ms with
> rohm,hw-timeout-ms
>
> .../bindings/mfd/rohm,bd9576-pmic.yaml | 123 ++++++++++++++++++
> 1 file changed, 123 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd9576-pmic.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-09-29 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 8:14 [PATCH v3 0/4] Support ROHM BD9576MUF and BD9573MUF PMICs Matti Vaittinen
2020-09-29 8:15 ` [PATCH v3 1/4] dt_bindings: mfd: Add " Matti Vaittinen
2020-09-29 14:53 ` Rob Herring [this message]
2020-09-29 8:16 ` [PATCH v3 2/4] mfd: Support ROHM BD9576MUF and BD9573MUF Matti Vaittinen
2020-09-29 8:17 ` [PATCH v3 3/4] wdt: Support wdt on " Matti Vaittinen
2020-10-01 15:30 ` Guenter Roeck
2020-09-29 8:17 ` [PATCH v3 4/4] MAINTAINERS: Add ROHM BD9576MUF and BD9573MUF drivers Matti Vaittinen
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=20200929145319.GA575227@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-power@fi.rohmeurope.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.