From: Rob Herring <robh@kernel.org>
To: Drew Fustini <dfustini@baylibre.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh+dt@kernel.org>, Dave Gerlach <d-gerlach@ti.com>,
linux-kernel@vger.kernel.org, Nishanth Menon <nm@ti.com>,
Tony Lindgren <tony@atomide.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
devicetree@vger.kernel.org, Keerthy <j-keerthy@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] dt-bindings: wkup-m3-ipc: Add ti,scale-data-fw property
Date: Fri, 29 Apr 2022 17:14:24 -0500 [thread overview]
Message-ID: <YmxjQCckMnE8de6s@robh.at.kernel.org> (raw)
In-Reply-To: <20220426193253.663582-2-dfustini@baylibre.com>
On Tue, 26 Apr 2022 12:32:52 -0700, Drew Fustini wrote:
> From: Dave Gerlach <d-gerlach@ti.com>
>
> Add documentation for ti,scale-data-fw property to enable I2C PMIC
> voltage scaling during deep sleep. The property contains the name of a
> binary file for the CM3 firmware to load.
>
> Based on previous work by Russ Dill.
>
> Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> [dfustini: split from driver patch and convert to json-schema]
> Signed-off-by: Drew Fustini <dfustini@baylibre.com>
> ---
> Changes from v1:
> - change 'ti,scale-data-fw' to 'firmware-name'
> - add 'firmware-name' property to the examples
>
> .../devicetree/bindings/soc/ti/wkup-m3-ipc.yaml | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
Applied, thanks!
next prev parent reply other threads:[~2022-04-29 22:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 19:32 [PATCH v2 0/2] soc: ti: wkup_m3_ipc: support i2c voltage scaling Drew Fustini
2022-04-26 19:32 ` [PATCH v2 1/2] dt-bindings: wkup-m3-ipc: Add ti,scale-data-fw property Drew Fustini
2022-04-29 22:14 ` Rob Herring [this message]
2022-04-29 22:15 ` Rob Herring
2022-04-26 19:32 ` [PATCH v2 2/2] soc: ti: wkup_m3_ipc: Add support for i2c voltage scaling Drew Fustini
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=YmxjQCckMnE8de6s@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dfustini@baylibre.com \
--cc=j-keerthy@ti.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).