All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ludvig Pärsson" <Ludvig.Parsson@axis.com>
To: "sumit.garg@linaro.org" <sumit.garg@linaro.org>,
	"Ludvig Pärsson" <Ludvig.Parsson@axis.com>
Cc: "jens.wiklander@linaro.org" <jens.wiklander@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	kernel <kernel@axis.com>,
	"op-tee@lists.trustedfirmware.org"
	<op-tee@lists.trustedfirmware.org>
Subject: Re: [PATCH] tee: optee: Populate child nodes in probe function
Date: Fri, 11 Nov 2022 13:16:41 +0000	[thread overview]
Message-ID: <02a899a1807274e2d0fa20e0d6059db00839d9ec.camel@axis.com> (raw)
In-Reply-To: <CAFA6WYPgW0ya3+yiD49QH3q4nLj1rUyEPye_x2engtihYVaNuA@mail.gmail.com>

On Fri, 2022-11-11 at 15:27 +0530, Sumit Garg wrote:
> On Thu, 10 Nov 2022 at 17:39, Ludvig Pärsson
> <Ludvig.Parsson@axis.com> wrote:
> > 
> > On Thu, 2022-11-10 at 16:23 +0530, Sumit Garg wrote:
> > > On Wed, 9 Nov 2022 at 21:37, Ludvig Pärsson < 
> > > ludvig.parsson@axis.com>
> > > wrote:
> > > > 
> > > > Currently there is no dependency between the "linaro,scmi-
> > > > optee"
> > > > driver
> > > > and the tee_core. If the scmi-optee driver gets probed before
> > > > the
> > > > tee_bus_type is initialized, then we will get an unwanted error
> > > > print.
> > > > 
> > > 
> > > What error print do you observe? I suppose this case is already
> > > handled by scmi optee driver via -EPROBE_DEFER.
> > > 
> > > -Sumit
> > > 
> > Hi Sumit,
> > 
> > The error print is in driver_register().
> > 
> > This is kind of what happens:
> > scmi_driver_init()
> > scmi_probe()
> >     scmi_optee_link_supplier()
> >         scmi_optee_init()
> >             driver_register() <--- pr_err() if tee_bus_type is not
> > initialized
> > tee_init() <--- tee_bus_type gets initialized here
> > 
> > The scmi_optee_link_supplier() will always return -EPROBE_DEFER the
> > first time because scmi_optee_private is initialized in
> > scmi_optee_service_probe, which is only called after the driver is
> > registered in scmi_optee_init. Right now the driver_register fails
> > because tee_bus_type is not initialized which is printing the
> > unwanted
> > error print. Another side effect of this is that
> > scmi_optee_link_supplier() will return -EPROBE_DEFER a second time,
> > and
> > scmi_probe will be successful the third time instead of the second
> > time.
> 
> Thanks for the report. It rather looks like an inter subsystem
> dependency problem. Check if this [1] patch resolves your problem?
> 
> [1] https://lkml.org/lkml/2022/11/11/329
> 
> -Sumit
> 
Yes, this solves the problem, but I don't think the maintainer for the
SCMI subsystem likes the solution. Earlier this week I discussed this
problem with Sudeep, Cristian and Etienne that are CCed in the
submission you linked. Changing the initcall level was one of my
suggestions which got instantly rejected. We agreed that the solution
in the patch i submitted was probably the best one, but maybe they will
change their minds.

BR,
Ludvig

> > 
> > BR,
> > Ludvig
> > 
> > > > This patch enables putting scmi-optee nodes as children to the
> > > > optee
> > > > node in devicetree, which indirectly creates the missing
> > > > dependency.
> > > > 
> > > > Signed-off-by: Ludvig Pärsson <ludvig.parsson@axis.com>
> > > > ---
> > > >  drivers/tee/optee/smc_abi.c | 5 +++++
> > > >  1 file changed, 5 insertions(+)
> > > > 
> > > > diff --git a/drivers/tee/optee/smc_abi.c
> > > > b/drivers/tee/optee/smc_abi.c
> > > > index a1c1fa1a9c28..be6f02fd5a7f 100644
> > > > --- a/drivers/tee/optee/smc_abi.c
> > > > +++ b/drivers/tee/optee/smc_abi.c
> > > > @@ -1533,6 +1533,11 @@ static int optee_probe(struct
> > > > platform_device *pdev)
> > > >         if (rc)
> > > >                 goto err_disable_shm_cache;
> > > > 
> > > > +       /* Populate any dependent child node (if any) */
> > > > +       rc = devm_of_platform_populate(&pdev->dev);
> > > > +       if (rc)
> > > > +               goto err_disable_shm_cache;
> > > > +
> > > >         pr_info("initialized driver\n");
> > > >         return 0;
> > > > 
> > > > --
> > > > 2.30.2
> > > > 
> > 


  reply	other threads:[~2022-11-11 13:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 16:07 [PATCH] tee: optee: Populate child nodes in probe function Ludvig Pärsson
2022-11-10 10:53 ` Sumit Garg
2022-11-10 12:09   ` Ludvig Pärsson
2022-11-11  9:57     ` Sumit Garg
2022-11-11 13:16       ` Ludvig Pärsson [this message]
2022-11-11 16:13 ` Sudeep Holla
2022-11-14  6:38   ` Sumit Garg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=02a899a1807274e2d0fa20e0d6059db00839d9ec.camel@axis.com \
    --to=ludvig.parsson@axis.com \
    --cc=jens.wiklander@linaro.org \
    --cc=kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=sumit.garg@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.