linux-kernel - Re: [PATCH] of: property: fw_devlink: Add support for "mmc-pwrseq"

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: <176849790816.916369.13545562565648281883.robh@kernel.org>
Date: Thu, 15 Jan 2026 11:25:10 -0600
From: "Rob Herring (Arm)" <robh@...nel.org>
To: Francesco Valla <francesco@...la.it>
Cc: linux-kernel@...r.kernel.org, Saravana Kannan <saravanak@...nel.org>,
	linux-mmc@...r.kernel.org, Ulf Hansson <ulf.hansson@...aro.org>,
	devicetree@...r.kernel.org
Subject: Re: [PATCH] of: property: fw_devlink: Add support for "mmc-pwrseq"


On Sat, 10 Jan 2026 16:27:59 +0100, Francesco Valla wrote:
> Add support for parsing MMC power sequencing (pwrseq) binding so that
> fw_devlink can enforce the dependency.
> 
> Signed-off-by: Francesco Valla <francesco@...la.it>
> ---
> Resending this patch as it slipped through the cracks (of my attention,
> at least).
> 
> Original submission is at [0]; there it appears as a v2 because it was
> the first time I used b4. It was also part of [1], which wasn't really
> a patchset but a follow-up to the boot time SIG meeting.
> 
> I added Ulf and CC'd the mmc list, hoping they can (more
> authoritatively than me) reply to Saravan's question:
> 
> """
> I took a quick look at the documentation. It's not clear to me that
> mmc-pwrseq always points to a supplier. Can someone with more
> experience on this confirm that is what it's supposed to point at?
> 
> Meaning if A lists B as pwrseq, is it always the case that B needs to
> be powered on? The binding documentation doesn't say anything about B
> needs to be powered on first. It's just saying A and B have an
> ordering requirement.
> 
> If the meaning of the binding is _ALWAYS_ B needs to be powered on
> first, then yes, this patch is correct and I can give a reviewed-by.
> """
> 
> [0] https://lore.kernel.org/all/20250930-mmc_pwrseq-v2-1-80a8c6be0fb0@valla.it/
> [1] https://lore.kernel.org/linux-embedded/20251126-beagleplay-probes-v1-0-c833defd4c9b@valla.it/T/
> 
> Thank you!
> 
> Regards,
> Francesco
> ---
>  drivers/of/property.c | 2 ++
>  1 file changed, 2 insertions(+)
> 

Applied, thanks!