[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210728153647.llr6bfhyja5ezkth@bogus>
Date: Wed, 28 Jul 2021 16:36:47 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Cristian Marussi <cristian.marussi@....com>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
virtualization@...ts.linux-foundation.org,
virtio-dev@...ts.oasis-open.org, james.quinlan@...adcom.com,
Jonathan.Cameron@...wei.com, f.fainelli@...il.com,
etienne.carriere@...aro.org, vincent.guittot@...aro.org,
souvik.chakravarty@....com, igor.skalkin@...nsynergy.com,
peter.hilber@...nsynergy.com, alex.bennee@...aro.org,
jean-philippe@...aro.org, mikhail.golubev@...nsynergy.com,
anton.yakovlev@...nsynergy.com, Vasyl.Vavrychuk@...nsynergy.com,
Sudeep Holla <sudeep.holla@....com>,
Andriy.Tryshnivskyy@...nsynergy.com
Subject: Re: [PATCH v6 15/17] firmware: arm_scmi: Add optional
link_supplier() transport op
On Mon, Jul 12, 2021 at 03:18:31PM +0100, Cristian Marussi wrote:
> From: Peter Hilber <peter.hilber@...nsynergy.com>
>
> Some transports are also effectively registered with other kernel subsystem
> in order to be properly probed and initialized; as a consequence such kind
> of transports, and their related devices, might still not have been probed
> and initialized at the time the main SCMI core driver is probed.
>
> Add an optional .link_supplier() transport operation which can be used by
> the core SCMI stack to dynamically check if the transport is ready and
> dynamically link its device to the platform instance device.
>
To be precise,
s/platform instance device/SCMI platform instance device
--
Regards,
Sudeep
Powered by blists - more mailing lists