linux-kernel - Re: [PATCH] arm64: dts: ti: k3-j7200: Add node to disable loopback connection

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: <173583563568.269479.10047461594837475356.b4-ty@ti.com>
Date: Thu, 2 Jan 2025 10:34:03 -0600
From: Nishanth Menon <nm@...com>
To: <vigneshr@...com>, <kristo@...nel.org>, <robh@...nel.org>,
        <krzk+dt@...nel.org>, <conor+dt@...nel.org>,
        Anurag Dutta <a-dutta@...com>
CC: Nishanth Menon <nm@...com>, <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <u-kumar1@...com>, <vaishnav.a@...com>
Subject: Re: [PATCH] arm64: dts: ti: k3-j7200: Add node to disable loopback connection

Hi Anurag Dutta,

On Wed, 27 Nov 2024 13:26:44 +0530, Anurag Dutta wrote:
> CTRLMMR_MCU_SPI1_CTRL register controls if MCU_SPI1 is directly
> connected to SPI3 in the MAIN Domain (default) or if MCU_SPI1
> and SPI3 are independently pinned out. By default, the field
> SPI1_LINKDIS (Bit 0) is set to 0h. In order to disable the direct
> connection, the SPI1_LINKDIS (Bit 0) needs to be set to 1h. Model
> this functionality as a "reg-mux" device and based on the idle-state
> property, enable/disable the connection bewtween MCU_SPI1 and MAIN_SPI3.
> 
> [...]

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

[1/1] arm64: dts: ti: k3-j7200: Add node to disable loopback connection
      commit: 6b51892b31fe83fe7cc8cf69e4bf7721cf08951b

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