From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Etienne Carriere <etienne.carriere@linaro.org>
Cc: Jens Wiklander <jens.wiklander@linaro.org>,
u-boot@lists.denx.de,
Patrick Delaunay <patrick.delaunay@foss.st.com>
Subject: Re: [PATCH] tee: optee: rework TA bus scanning code
Date: Fri, 26 Aug 2022 12:19:08 +0300 [thread overview]
Message-ID: <YwiQDMhEa2FAGb2i@hades> (raw)
In-Reply-To: <CAN5uoS8EH9pGjLnTPVcTWwa5ebnZkup8N6nCzJbOyyppFXz8hw@mail.gmail.com>
Hey Etienne, Jens
[...]
> > > - if (IS_ENABLED(CONFIG_RNG_OPTEE)) {
> > > - ret = device_bind_driver(dev, "optee-rng", "optee-rng", &child);
> > > +
> > > + for (i = 0; i < MAX_TEE_BUS_DEV_COUNT; i++) {
>
> I would use ARRAY_SIZE(optee_bus_probe) straight here. Macro
> indirection is not really useful imho.
Sure
>
> > > + ret = device_bind_driver(dev, optee_bus_probe[i].drv_name,
> > > + optee_bus_probe[i].dev_name, &child);
> > > if (ret)
> > > return ret;
> >
> > I wonder which behaviour is most useful. Disable OP-TEE support
> > completely if there's some error when binding dependent drivers or to
> > just complain a bit but continue.
>
> I agree with you, this should better print the status and proceed with
> the next driver.
> There are other occurrences of such behaviour in U-Boot.
I also agree, however this changes the behaviour of *existing* code, which
I tried to avoid. Since you both think it's better, I'll just add a
log_err() on v2 and continue.
Thanks
/Ilias
>
> Br,
> etienne
>
>
> >
> > Cheers,
> > Jens
> >
> >
> > >
> > > }
> > > --
> > > 2.34.1
> > >
prev parent reply other threads:[~2022-08-26 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 8:11 [PATCH] tee: optee: rework TA bus scanning code Ilias Apalodimas
2022-08-26 8:46 ` Jens Wiklander
2022-08-26 9:07 ` Etienne Carriere
2022-08-26 9:19 ` Ilias Apalodimas [this message]
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=YwiQDMhEa2FAGb2i@hades \
--to=ilias.apalodimas@linaro.org \
--cc=etienne.carriere@linaro.org \
--cc=jens.wiklander@linaro.org \
--cc=patrick.delaunay@foss.st.com \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox