From: Rob Herring <robh@kernel.org>
To: Drew Fustini <dfustini@baylibre.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Dave Gerlach <d-gerlach@ti.com>, Tony Lindgren <tony@atomide.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Keerthy <j-keerthy@ti.com>
Subject: Re: [PATCH 1/2] dt-bindings: wkup-m3-ipc: Add ti,scale-data-fw property
Date: Mon, 25 Apr 2022 11:22:20 -0500 [thread overview]
Message-ID: <YmbKvN00F6vGawpE@robh.at.kernel.org> (raw)
In-Reply-To: <20220425052806.484590-2-dfustini@baylibre.com>
On Sun, Apr 24, 2022 at 10:28:05PM -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>
> ---
> .../devicetree/bindings/soc/ti/wkup-m3-ipc.yaml | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/soc/ti/wkup-m3-ipc.yaml b/Documentation/devicetree/bindings/soc/ti/wkup-m3-ipc.yaml
> index 88d690de050c..d2c248d82384 100644
> --- a/Documentation/devicetree/bindings/soc/ti/wkup-m3-ipc.yaml
> +++ b/Documentation/devicetree/bindings/soc/ti/wkup-m3-ipc.yaml
> @@ -40,6 +40,12 @@ description: |+
> override the pin's existing bias (pull-up/pull-down) and value (high/low) when
> IO isolation is active.
>
> + Support for I2C PMIC Voltage Scaling
> + ====================================
> + It is possible to pass the name of a binary file to load into the CM3 memory.
> + The binary data is the I2C sequences for the CM3 to send out to the PMIC
> + during low power mode entry.
> +
> properties:
> compatible:
> enum:
> @@ -67,6 +73,11 @@ properties:
> mbox_wkupm3 child node.
> maxItems: 1
>
> + ti,scale-data-fw:
> + $ref: /schemas/types.yaml#/definitions/string
> + description:
> + Name of the firmware binary in /lib/firmware to copy to CM3 aux data
The location of firmware files is up to the OS.
Is there other firmware? If not, 'firmware-name' is the somewhat
standard property for this.
What's the default name?
> +
> ti,vtt-gpio-pin:
> $ref: /schemas/types.yaml#/definitions/uint32
> description: GPIO pin connected to enable pin on VTT regulator
> --
> 2.32.0
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-25 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 5:28 [PATCH 0/2] soc: ti: wkup_m3_ipc: support i2c voltage scaling Drew Fustini
2022-04-25 5:28 ` [PATCH 1/2] dt-bindings: wkup-m3-ipc: Add ti,scale-data-fw property Drew Fustini
2022-04-25 16:22 ` Rob Herring [this message]
2022-04-26 19:28 ` Drew Fustini
2022-04-25 5:28 ` [PATCH 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=YmbKvN00F6vGawpE@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=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).