From: Drew Fustini <dfustini@baylibre.com>
To: Rob Herring <robh+dt@kernel.org>,
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>
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: Add support for IO Isolation
Date: Thu, 14 Apr 2022 12:12:48 -0700 [thread overview]
Message-ID: <20220414191250.2969282-1-dfustini@baylibre.com> (raw)
TI AM437x SoCs support isolation of the IOs so that control is taken
from the peripheral they are connected to and overridden by values
present in the control register for that pad. This series documents a
new property 'ti,set-io-isolation' and updates the wkup_m3_ipc driver to
inform the CM3 firmware when that property is set.
A prerequisite for this series is:
[PATCH v2 0/2] soc: ti: wkup_m3_ipc: support vtt toggle
https://lore.kernel.org/lkml/20220409211215.2529387-1-dfustini@baylibre.com/T/
Changes from v1:
- correct typo of 'ti,set-io-isolation' property
- make 'ti,set-io-isolation' only valid for 'ti,am4372-wkup-m3-ipc'
Dave Gerlach (1):
soc: ti: wkup_m3_ipc: Add support for IO Isolation
Drew Fustini (1):
dt-bindings: wkup-m3-ipc: Add ti,set-io-isolation property
.../bindings/soc/ti/wkup-m3-ipc.yaml | 79 +++++++++++++++++--
drivers/soc/ti/wkup_m3_ipc.c | 14 +++-
include/linux/wkup_m3_ipc.h | 1 +
3 files changed, 87 insertions(+), 7 deletions(-)
--
2.32.0
next reply other threads:[~2022-04-14 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 19:12 Drew Fustini [this message]
2022-04-14 19:12 ` [PATCH v2 1/2] dt-bindings: wkup-m3-ipc: Add ti,set-io-isolation property Drew Fustini
2022-04-14 19:12 ` [PATCH v2 2/2] soc: ti: wkup_m3_ipc: Add support for IO Isolation 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=20220414191250.2969282-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®