[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172899815900.948565.3328227114725674760.b4-ty@arm.com>
Date: Tue, 15 Oct 2024 14:16:34 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: linux-arm-kernel@...ts.infreadead.org,
Florian Fainelli <florian.fainelli@...adcom.com>
Cc: Sudeep Holla <sudeep.holla@....com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Cristian Marussi <cristian.marussi@....com>,
devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
arm-scmi@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
justin.chen@...adcom.com,
opendmb@...il.com,
kapil.hali@...adcom.com,
bcm-kernel-feedback-list@...adcom.com,
Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v2] firmware: arm_scmi: Give SMC transport precedence over mailbox
On Mon, 07 Oct 2024 16:54:13 -0700, Florian Fainelli wrote:
> Broadcom STB platforms have for historical reasons included both
> "arm,scmi-smc" and "arm,scmi" in their SCMI Device Tree node compatible
> string, in that order.
>
> After the commit cited in the Fixes tag and with a kernel configuration
> that enables both the SMC and the Mailbox transports, we would probe
> the mailbox transport, but fail to complete since we would not have a
> mailbox driver available. With each SCMI transport being a platform
> driver with its own set of compatible strings to match, rather than an
> unique platform driver entry point, we no longer match from most
> specific to least specific. There is also no simple way for the mailbox
> driver to return -ENODEV and let another platform driver attempt
> probing. This leads to a platform with no SCMI provider, therefore all
> drivers depending upon SCMI resources are put on deferred probe forever.
>
> [...]
Applied to sudeep.holla/linux (for-next/scmi/fixes), thanks!
[1/1] firmware: arm_scmi: Give SMC transport precedence over mailbox
https://git.kernel.org/sudeep.holla/c/db8f0b808886
--
Regards,
Sudeep
Powered by blists - more mailing lists