[PATCH v9 1/7] firmware: smccc: Add an Arm SMCCC bus
Sudeep Holla
sudeep.holla at kernel.org
Thu Sep 3 07:13:45 PDT 2026
On Thu, Sep 03, 2026 at 09:57:18AM -0300, Jason Gunthorpe wrote:
> On Thu, Sep 03, 2026 at 02:22:51PM +0530, Aneesh Kumar K.V wrote:
>
> > I have updated the bus to match devices using func_id.
>
> Did you have any thoughts on how to handle ARM's versioning scheme
> too?
>
> I'm not sure what the rules are but it seems like if the major changes
> then the API is incompatible? So shouldn't every driver advertise a
> supported major, and the major be in the modalias and checked by match
> too?
>
Just curious as how this should work with any v1.x firmwares in the wild
once the driver updates the supported major version to say v2.0
Is there a way to set the supported major version in the driver via
some module parameter that the old systems then can make use of. Just
random thoughts/queries to understand how they all fit it eventually for
the wild variety of f/w we need to support irrespective of what is the
supported max major version the driver advertises.
--
Regards,
Sudeep
More information about the linux-arm-kernel
mailing list