From: Nishanth Menon <nm@ti.com>
To: Santosh Shilimkar <ssantosh@kernel.org>,
Dave Gerlach <d-gerlach@ti.com>, Tony Lindgren <tony@atomide.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Drew Fustini <dfustini@baylibre.com>
Cc: Nishanth Menon <nm@ti.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>
Subject: Re: (subset) [PATCH v3 0/2] soc: ti: wkup_m3_ipc: Add support for IO Isolation
Date: Tue, 3 May 2022 08:08:54 -0500 [thread overview]
Message-ID: <165158332118.6421.15725754853562188300.b4-ty@ti.com> (raw)
In-Reply-To: <20220414192722.2978837-1-dfustini@baylibre.com>
Hi Drew Fustini,
On Thu, 14 Apr 2022 12:27:22 -0700, Drew Fustini wrote:
> 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/
>
> [...]
I have applied the following to branch ti-drivers-soc-next on [1].
Thank you!
[2/2] soc: ti: wkup_m3_ipc: Add support for IO Isolation
commit: 1dcbae86ee669bdb0338954cd0136863f5c96c0a
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2022-05-03 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 19:27 [PATCH v3 0/2] soc: ti: wkup_m3_ipc: Add support for IO Isolation Drew Fustini
2022-04-14 19:27 ` [PATCH v3 1/2] dt-bindings: wkup-m3-ipc: Add ti,set-io-isolation property Drew Fustini
2022-04-14 19:44 ` Drew Fustini
2022-04-19 13:04 ` Rob Herring
2022-04-14 19:27 ` [PATCH v3 2/2] soc: ti: wkup_m3_ipc: Add support for IO Isolation Drew Fustini
2022-04-21 6:56 ` [PATCH v3 0/2] " Tony Lindgren
2022-04-22 5:10 ` Drew Fustini
2022-04-26 6:45 ` Tony Lindgren
2022-05-03 13:08 ` Nishanth Menon [this message]
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=165158332118.6421.15725754853562188300.b4-ty@ti.com \
--to=nm@ti.com \
--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=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).