linux-kernel - Re: [PATCH v2] arm64: dts: ti: k3-j721e-mcu-wakeup: Add MCU domain ESM instance

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: <169633065056.2221719.3724450328166244211.b4-ty@ti.com>
Date:   Tue, 3 Oct 2023 16:30:45 +0530
From:   Vignesh Raghavendra <vigneshr@...com>
To:     <robh+dt@...nel.org>, <conor+dt@...nel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        Neha Malcom Francis <n-francis@...com>
CC:     Vignesh Raghavendra <vigneshr@...com>, <nm@...com>,
        <kristo@...nel.org>, <u-kumar1@...com>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-j721e-mcu-wakeup: Add MCU domain ESM instance

Hi Neha Malcom Francis,

On Tue, 26 Sep 2023 19:58:10 +0530, Neha Malcom Francis wrote:
> Currently J721E defines only the main_esm in DTS. Add node for mcu_esm
> as well.
> 
> According to J721E TRM (12.11.2.2 ESM Environment) [1], we see that the
> interrupt line from ESMi (main_esm) is routed to MCU_ESM (mcu_esm). This
> is MCU_ESM0_LVL_IN_95 with interrupt ID 95. Configure mcu_esm
> accordingly so that errors from main_esm are routed to mcu_esm and
> handled.
> 
> [...]

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

[1/1] arm64: dts: ti: k3-j721e-mcu-wakeup: Add MCU domain ESM instance
      commit: cd5b5c5a527b7fd25260be7e9013ee9c97efc2c0

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
--
Vignesh