linux-kernel - Re: [PATCH v2 0/2] Add Deep Sleep pinmux macros for TI's K3 SoCs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <173524493391.82332.13942073781133579692.b4-ty@ti.com>
Date: Thu, 26 Dec 2024 14:29:55 -0600
From: Nishanth Menon <nm@...com>
To: <vigneshr@...com>, <kristo@...nel.org>, <robh@...nel.org>,
        <krzk+dt@...nel.org>, <conor+dt@...nel.org>,
        Siddharth Vadapalli
	<s-vadapalli@...com>
CC: Nishanth Menon <nm@...com>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
        <srk@...com>
Subject: Re: [PATCH v2 0/2] Add Deep Sleep pinmux macros for TI's K3 SoCs

Hi Siddharth Vadapalli,

On Thu, 05 Dec 2024 17:31:27 +0530, Siddharth Vadapalli wrote:
> This series introduces deep sleep macros which are common to TI's K3
> SoCs and can be used to configure the behavior of SoC pins during Deep
> Sleep mode. Additionally, support for SoC wakeup with USB1 on AM62x
> based SoCs is added with the help of the newly introduced deep sleep
> macros.
> 
> v1:
> https://lore.kernel.org/r/20241112115650.988943-1-s-vadapalli@ti.com
> Changes since v1:
> - Rebased on next-20241204.
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/2] arm64: dts: ti: k3-pinctrl: Introduce deep sleep macros
      commit: 325aa0f6b36eab0fe7d7efdb49b55cf7d664424a
[2/2] arm64: dts: ti: k3-am62x-sk-common: Support SoC wakeup using USB1 wakeup
      commit: 527f884d2d94981016e181dcbd4c4b5bf597c0ad

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] https://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