From: Drew Fustini <dfustini@baylibre.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Dave Gerlach <d-gerlach@ti.com>, Tony Lindgren <tony@atomide.com>,
Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Drew Fustini <dfustini@baylibre.com>
Subject: [PATCH v2 0/2] soc: ti: wkup_m3_ipc: support vtt toggle
Date: Sat, 9 Apr 2022 14:12:13 -0700 [thread overview]
Message-ID: <20220409211215.2529387-1-dfustini@baylibre.com> (raw)
This series enables the Cortex M3 processor found in AM33xx and AM43xx
SoCs to toggle the VTT regulator during low power mode transitions.
I recently converted the Wakeup M3 IPC bindings to YAML. Rob has applied
that patch [1]. It is a prerequisite for the wkup-m3-ipc.yaml patch in
this series.
[1] https://lore.kernel.org/linux-devicetree/YlCACSZx5xsPSwNC@robh.at.kernel.org/
Changes since v1:
- Removed unnecessary "ti,needs-vtt-toggle" property
Dave Gerlach (1):
soc: ti: wkup_m3_ipc: Add support for toggling VTT regulator
Drew Fustini (1):
dt-bindings: wkup-m3-ipc: Add vtt toggle gpio pin property
.../bindings/soc/ti/wkup-m3-ipc.yaml | 13 ++++++++++
drivers/soc/ti/wkup_m3_ipc.c | 26 +++++++++++++++++--
include/linux/wkup_m3_ipc.h | 1 +
3 files changed, 38 insertions(+), 2 deletions(-)
--
2.32.0
next reply other threads:[~2022-04-09 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 21:12 Drew Fustini [this message]
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
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=20220409211215.2529387-1-dfustini@baylibre.com \
--to=dfustini@baylibre.com \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--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
all inboxes | Powered by JetHome®