linux-kernel - Re: [PATCH v2 0/2] Enable SA2UL support on AM64X

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: <166204207692.900930.17592300086074188441.b4-ty@ti.com>
Date:   Thu, 1 Sep 2022 19:53:14 +0530
From:   Vignesh Raghavendra <vigneshr@...com>
To:     <nm@...com>, Jayesh Choudhary <j-choudhary@...com>,
        <devicetree@...r.kernel.org>
CC:     Vignesh Raghavendra <vigneshr@...com>, <robh+dt@...nel.org>,
        <linux-arm-kernel@...ts.infradead.org>, <kristo@...nel.org>,
        <linux-kernel@...r.kernel.org>, <krzysztof.kozlowski+dt@...aro.org>
Subject: Re: [PATCH v2 0/2] Enable SA2UL support on AM64X

Hi Jayesh Choudhary,

On Mon, 11 Jul 2022 14:27:41 +0530, Jayesh Choudhary wrote:
> This series enables sa2ul support for TI SoC AM64X.
> It is based on another series posted by Suman Anna:
> <https://lore.kernel.org/linux-arm-kernel/20210514210725.32720-1-s-anna@ti.com/>
> 
> rng node has been disabled due to its indirect access from OP-TEE.
> 
> Since the sa2ul hardware is being used by OP-TEE as well,
> it should be requested using shared TI-SCI flag. So the flag
> has been changed from TI-SCI-EXCLUSIVE to TI-SCI-SHARED.
> 
> [...]

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

[1/2] arm64: dts: ti: k3-am64: Add SA2UL address space to Main CBASS ranges
      commit: e66e5b2d7f43d92fffb940988ed2822a1b28143b
[2/2] arm64: dts: ti: k3-am64-main: Enable crypto accelerator
      commit: e170ae6dd67a00f750996820d55b144c5189be66

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