linux-kernel - Re: [PATCH 1/2] arm64: dts: ti: k3-j721e-sk: Fix reversed C6x carveout locations

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: <172487018381.3436753.17446528403419157131.b4-ty@ti.com>
Date: Wed, 28 Aug 2024 13:37:39 -0500
From: Nishanth Menon <nm@...com>
To: Vignesh Raghavendra <vigneshr@...com>, Tero Kristo <kristo@...nel.org>,
        Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski
	<krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>, Andrew Davis <afd@...com>
CC: Nishanth Menon <nm@...com>, <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] arm64: dts: ti: k3-j721e-sk: Fix reversed C6x carveout locations

Hi Andrew Davis,

On Thu, 01 Aug 2024 13:12:31 -0500, Andrew Davis wrote:
> The DMA carveout for the C6x core 0 is at 0xa6000000 and core 1 is at
> 0xa7000000. These are reversed in DT. While both C6x can access either
> region, so this is not normally a problem, but if we start restricting
> the memory each core can access (such as with firewalls) the cores
> accessing the regions for the wrong core will not work. Fix this here.
> 
> 
> [...]

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

[1/2] arm64: dts: ti: k3-j721e-sk: Fix reversed C6x carveout locations
      commit: 9f3814a7c06b7c7296cf8c1622078ad71820454b
[2/2] arm64: dts: ti: k3-j721e-beagleboneai64: Fix reversed C6x carveout locations
      commit: 1a314099b7559690fe23cdf3300dfff6e830ecb1

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