linux-kernel - Re: [PATCH v3 0/4] J722S: Disable WIZ0 and WIZ1 in SoC file

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: <174500262306.95371.2904108787224104131.b4-ty@ti.com>
Date: Fri, 18 Apr 2025 13:57:29 -0500
From: Nishanth Menon <nm@...com>
To: <vigneshr@...com>, <kristo@...nel.org>, <robh@...nel.org>,
        <krzk+dt@...nel.org>, <conor+dt@...nel.org>, <rogerq@...nel.org>,
        <u-kumar1@...com>, Siddharth Vadapalli <s-vadapalli@...com>
CC: Nishanth Menon <nm@...com>, <stable@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>, <srk@...com>
Subject: Re: [PATCH v3 0/4] J722S: Disable WIZ0 and WIZ1 in SoC file

Hi Siddharth Vadapalli,

On Thu, 17 Apr 2025 18:02:42 +0530, Siddharth Vadapalli wrote:
> This series disables the "serdes_wiz0" and "serdes_wiz1" device-tree
> nodes in the J722S SoC file and enables them in the board files where
> they are required along with "serdes0" and "serdes1". There are two
> reasons behind this change:
> 1. To follow the existing convention of disabling nodes in the SoC file
>    and enabling them in the board file as required.
> 2. To address situations where a board file hasn't explicitly disabled
>    "serdes_wiz0" and "serdes_wiz1" (example: am67a-beagley-ai.dts)
>    as a result of which booting the board displays the following errors:
>      wiz bus@...00:phy@...0000: probe with driver wiz failed with error -12
>      ...
>      wiz bus@...00:phy@...0000: probe with driver wiz failed with error -12
> 
> [...]

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

[1/4] arm64: dts: ti: k3-j722s-evm: Enable "serdes_wiz0" and "serdes_wiz1"
      commit: 9d76be5828be44ed7a104cc21b4f875be4a63322
[2/4] arm64: dts: ti: k3-j722s-main: Disable "serdes_wiz0" and "serdes_wiz1"
      commit: 320d8a84f6f045dc876d4c2983f9024c7ac9d6df
[3/4] arm64: dts: ti: k3-j722s-main: don't disable serdes0 and serdes1
      commit: 3f7523bf8c35f96e0309d420d9f89e300c97fc20
[4/4] arm64: dts: ti: k3-j722s-evm: drop redundant status within serdes0/serdes1
      commit: 2a36e8656836f5897508e61d46d22fe344af6426

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