mbox series

[v2,0/2] Add Deep Sleep pinmux macros for TI's K3 SoCs

Message ID 20241205120134.754664-1-s-vadapalli@ti.com (mailing list archive)
Headers show
Series Add Deep Sleep pinmux macros for TI's K3 SoCs | expand

Message

Siddharth Vadapalli Dec. 5, 2024, 12:01 p.m. UTC
Hello,

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.

Series is based on linux-next tagged next-20241204.

Regards,
Siddharth.

Siddharth Vadapalli (2):
  arm64: dts: ti: k3-pinctrl: Introduce deep sleep macros
  arm64: dts: ti: k3-am62x-sk-common: Support SoC wakeup using USB1
    wakeup

 .../arm64/boot/dts/ti/k3-am62x-sk-common.dtsi |  2 +-
 arch/arm64/boot/dts/ti/k3-pinctrl.h           | 19 +++++++++++++++++++
 2 files changed, 20 insertions(+), 1 deletion(-)

Comments

Nishanth Menon Dec. 26, 2024, 8:29 p.m. UTC | #1
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