linux-kernel - Re: [PATCH v2] firmware: ti_sci: set IO Isolation only if the firmware is capable

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <176218288382.3559260.12524155435608432109.b4-ty@ti.com>
Date: Mon, 3 Nov 2025 09:14:53 -0600
From: Nishanth Menon <nm@...com>
To: Tero Kristo <kristo@...nel.org>, Santosh Shilimkar <ssantosh@...nel.org>,
	"Thomas Richard (TI.com)" <thomas.richard@...tlin.com>
CC: Nishanth Menon <nm@...com>, Thomas Petazzoni
	<thomas.petazzoni@...tlin.com>, Gregory CLEMENT
	<gregory.clement@...tlin.com>, Richard Genoud <richard.genoud@...tlin.com>,
	Udit Kumar <u-kumar1@...com>, Prasanth Mantena <p-mantena@...com>, "Abhash
 Kumar" <a-kumar2@...com>, <linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] firmware: ti_sci: set IO Isolation only if the firmware is capable

Hi Thomas Richard (TI.com),

On Fri, 31 Oct 2025 13:44:56 +0100, Thomas Richard (TI.com) wrote:
> Prevent calling ti_sci_cmd_set_io_isolation() on firmware that does not
> support the IO_ISOLATION capability. Add the MSG_FLAG_CAPS_IO_ISOLATION
> capability flag and check it before attempting to set IO isolation during
> suspend/resume operations.
> 
> Without this check, systems with older firmware may experience undefined
> behavior or errors when entering/exiting suspend states.
> 
> [...]

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

[1/1] firmware: ti_sci: set IO Isolation only if the firmware is capable
      commit: 999e9bc953e321651d69556fdd5dfd178f96f128

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
https://ti.com/opensource