Re: [PATCH v2 0/4] Rework SCMI transport drivers probing sequence

On Sun, 10 May 2026 17:05:23 +0100, Cristian Marussi wrote:
> when the SCMI transports were split out into standalone drivers [1] the
> probe sequence was laid out in such a way that:
> 
>  - the transport drivers would have probed first, triggered by the firmware
>    driven discovery process (DT/ACPI)
> 
>  - afterwards the control would have been passed to the core SCMI stack
>    driver via the creation of a dedicated device that would have inherited
>    the original firmware descriptor (since that same DT/ACPI node would
>    have been still needed by the SCMI core driver to be parsed)
> 
> [...]

I haven't seen any reports of failure in -next with these, so I am happy
to take it for v7.2.

Applied to sudeep.holla/linux (for-next/scmi/updates), thanks!

[1/4] firmware: arm_scmi: Add transport instance handles
      https://git.kernel.org/sudeep.holla/c/9dfae7d2edb4
[2/4] firmware: arm_scmi: Add a generic transport supplier
      https://git.kernel.org/sudeep.holla/c/ab6eb28a47d4
[3/4] firmware: arm_scmi: virtio: Rework transport probe sequence
      https://git.kernel.org/sudeep.holla/c/c08051901a55
[4/4] firmware: arm_scmi: optee: Rework transport probe sequence
      https://git.kernel.org/sudeep.holla/c/524abd2fa690

--
Regards,
Sudeep