From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Fabien DESSENNE <fabien.dessenne@st.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
Loic PALLARDY <loic.pallardy@st.com>,
Arnaud POULIQUEN <arnaud.pouliquen@st.com>,
"linux-remoteproc@vger.kernel.org"
<linux-remoteproc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] remoteproc: stm32: fix probe error case
Date: Tue, 12 Nov 2019 10:22:39 -0800 [thread overview]
Message-ID: <20191112182239.GA21530@yoga> (raw)
In-Reply-To: <392808fa-1504-233f-234b-0cca21886c17@st.com>
On Tue 12 Nov 06:09 PST 2019, Fabien DESSENNE wrote:
> Hi Bjorn,
>
>
> On 11/11/2019 11:04 PM, Bjorn Andersson wrote:
> > On Mon 07 Oct 00:39 PDT 2019, Fabien Dessenne wrote:
> >
> >> If the rproc driver is probed before the mailbox driver and if the rproc
> >> Device Tree node has some mailbox properties, the rproc driver probe
> >> shall be deferred instead of being probed without mailbox support.
> >>
> >> Signed-off-by: Fabien Dessenne <fabien.dessenne@st.com>
> >> ---
> >> Changes since v1: test IS_ERR() before checking PTR_ERR()
> >> ---
> >> drivers/remoteproc/stm32_rproc.c | 10 ++++++++--
> >> 1 file changed, 8 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/drivers/remoteproc/stm32_rproc.c b/drivers/remoteproc/stm32_rproc.c
> >> index 2cf4b29..a507332 100644
> >> --- a/drivers/remoteproc/stm32_rproc.c
> >> +++ b/drivers/remoteproc/stm32_rproc.c
> >> @@ -310,7 +310,7 @@ static const struct stm32_mbox stm32_rproc_mbox[MBOX_NB_MBX] = {
> >> }
> >> };
> >>
> >> -static void stm32_rproc_request_mbox(struct rproc *rproc)
> >> +static int stm32_rproc_request_mbox(struct rproc *rproc)
> >> {
> >> struct stm32_rproc *ddata = rproc->priv;
> >> struct device *dev = &rproc->dev;
> >> @@ -329,10 +329,14 @@ static void stm32_rproc_request_mbox(struct rproc *rproc)
> >>
> >> ddata->mb[i].chan = mbox_request_channel_byname(cl, name);
> >> if (IS_ERR(ddata->mb[i].chan)) {
> >> + if (PTR_ERR(ddata->mb[i].chan) == -EPROBE_DEFER)
> >> + return -EPROBE_DEFER;
> > If for some reason you get EPROBE_DEFER when i > 0 you need to
> > mbox_free_channel() channels [0..i) before returning.
>
> The mailbox framework returns EPROBE_DIFFER to inform that the mailbox
> provider has not registered yet. I do not expected to have a success
> followed by a EPROBE_DEFER error.
>
> But in the very special case where we use two different mailbox
> providers this may happen.
>
I agree, it's unlikely to ever cause any problems...
> I will send an updated version, thanks for pointing this.
>
I appreciate that.
Thanks,
Bjorn
> BR
>
> Fabien
>
> >
> > Regards,
> > Bjorn
> >
> >> dev_warn(dev, "cannot get %s mbox\n", name);
> >> ddata->mb[i].chan = NULL;
> >> }
> >> }
> >> +
> >> + return 0;
> >> }
> >>
> >> static int stm32_rproc_set_hold_boot(struct rproc *rproc, bool hold)
> >> @@ -596,7 +600,9 @@ static int stm32_rproc_probe(struct platform_device *pdev)
> >> if (ret)
> >> goto free_rproc;
> >>
> >> - stm32_rproc_request_mbox(rproc);
> >> + ret = stm32_rproc_request_mbox(rproc);
> >> + if (ret)
> >> + goto free_rproc;
> >>
> >> ret = rproc_add(rproc);
> >> if (ret)
> >> --
> >> 2.7.4
> >>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-11-12 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 7:39 [PATCH v2] remoteproc: stm32: fix probe error case Fabien Dessenne
2019-11-11 22:04 ` Bjorn Andersson
2019-11-12 14:09 ` Fabien DESSENNE
2019-11-12 18:22 ` Bjorn Andersson [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=20191112182239.GA21530@yoga \
--to=bjorn.andersson@linaro.org \
--cc=alexandre.torgue@st.com \
--cc=arnaud.pouliquen@st.com \
--cc=fabien.dessenne@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=loic.pallardy@st.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=ohad@wizery.com \
/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;
as well as URLs for NNTP newsgroup(s).