[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZNCvVrDdgiEUsIgc@hovoldconsulting.com>
Date: Mon, 7 Aug 2023 10:46:14 +0200
From: Johan Hovold <johan@...nel.org>
To: Maximilian Luz <luzmaximilian@...il.com>
Cc: Bjorn Andersson <andersson@...nel.org>,
Andy Gross <agross@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Ard Biesheuvel <ardb@...nel.org>,
Ilias Apalodimas <ilias.apalodimas@...aro.org>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Sudeep Holla <sudeep.holla@....com>,
Steev Klimaszewski <steev@...i.org>,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 2/3] firmware: qcom_scm: Add support for Qualcomm
Secure Execution Environment SCM interface
On Fri, Aug 04, 2023 at 10:11:18PM +0200, Maximilian Luz wrote:
> On 8/4/23 18:48, Johan Hovold wrote:
> > On Sun, Jul 30, 2023 at 06:19:03PM +0200, Maximilian Luz wrote:
> >> +MODULE_ALIAS("platform:qcom_qseecom");
> >
> > No need for MODULE_ALIAS() either.
>
> Oh right. As long as the module and device name match this should work
> automatically, correct? I forgot about that.
Yeah, the module alias is only used when determining which modules to
load.
The driver and platform device will still be matched and bound based on
their names.
Johan
Powered by blists - more mailing lists