linux-kernel - Re: [PATCH v2] firmware: ti_sci: Convert CPU latency constraint from us to ms

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: <174653683694.692511.6512121885048153662.b4-ty@ti.com>
Date: Tue, 6 May 2025 08:07:31 -0500
From: Nishanth Menon <nm@...com>
To: <kristo@...nel.org>, <ssantosh@...nel.org>, <d-gole@...com>,
        Kendall
 Willis <k-willis@...com>
CC: Nishanth Menon <nm@...com>, <khilman@...libre.com>, <msp@...libre.com>,
        <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] firmware: ti_sci: Convert CPU latency constraint from us to ms

Hi Kendall Willis,

On Mon, 28 Apr 2025 15:53:36 -0500, Kendall Willis wrote:
> Fix CPU resume latency constraint units sent to device manager through the
> TI SCI API. The device manager expects CPU resume latency to be in msecs
> which is passed in with the TI SCI API [1]. CPU latency constraints are
> set in userspace using the PM QoS framework which uses usecs as the unit.
> Since PM QoS uses usecs for units and the device manager expects msecs as
> the unit, TI SCI needs to convert from usecs to msecs before passing to
> device manager.
> 
> [...]

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

[1/1] firmware: ti_sci: Convert CPU latency constraint from us to ms
      commit: 9b808f7f395ae375a26e32046b680cf898dacc21

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