From: Rob Herring <robh@kernel.org>
To: Drew Fustini <dfustini@baylibre.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-kernel@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
Rob Herring <robh+dt@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
Nishanth Menon <nm@ti.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Dave Gerlach <d-gerlach@ti.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: wkup-m3-ipc: Add vtt toggle gpio pin property
Date: Wed, 13 Apr 2022 16:48:28 -0500 [thread overview]
Message-ID: <YldFLAVMWhcpn1QC@robh.at.kernel.org> (raw)
In-Reply-To: <20220409211215.2529387-2-dfustini@baylibre.com>
On Sat, 09 Apr 2022 14:12:14 -0700, Drew Fustini wrote:
> Document Wakeup M3 IPC property that indicates a GPIO pin is connected
> to the enable pin on DDR VTT regulator and can be toggled during low
> power mode transitions.
>
> Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
> [dfustini: converted to YAML, removed unnecessary "ti,needs-vtt-toggle"]
> Signed-off-by: Drew Fustini <dfustini@baylibre.com>
> ---
> .../devicetree/bindings/soc/ti/wkup-m3-ipc.yaml | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
Applied, thanks!
next prev parent reply other threads:[~2022-04-13 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 21:12 [PATCH v2 0/2] soc: ti: wkup_m3_ipc: support vtt toggle Drew Fustini
2022-04-09 21:12 ` [PATCH v2 1/2] dt-bindings: wkup-m3-ipc: Add vtt toggle gpio pin property Drew Fustini
2022-04-10 14:17 ` Krzysztof Kozlowski
2022-04-12 19:54 ` Rob Herring
2022-04-12 21:15 ` Drew Fustini
2022-04-13 21:48 ` Rob Herring [this message]
2022-04-09 21:12 ` [PATCH v2 2/2] soc: ti: wkup_m3_ipc: Add support for toggling VTT regulator Drew Fustini
2022-04-22 23:14 ` (subset) [PATCH v2 0/2] soc: ti: wkup_m3_ipc: support vtt toggle Nishanth Menon
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=YldFLAVMWhcpn1QC@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dfustini@baylibre.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).