From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Brian Norris <briannorris@chromium.org>,
ohad@wizery.com, linux-remoteproc@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
sibis@codeaurora.org
Subject: Re: [PATCH] remoteproc: qcom: q6v5: shore up resource probe handling
Date: Tue, 9 Oct 2018 23:19:20 -0700 [thread overview]
Message-ID: <20181010061920.GS12063@builder> (raw)
In-Reply-To: <CAD=FV=Vh4NWUS--dDU5N0b86ZoRd7kEj7Zuk5VCE=WkaRWp=tg@mail.gmail.com>
On Tue 09 Oct 16:34 PDT 2018, Doug Anderson wrote:
> Hi,
>
> On Tue, Oct 9, 2018 at 3:33 PM Brian Norris <briannorris@chromium.org> wrote:
> > + if (q6v5->wdog_irq < 0) {
> > + if (q6v5->wdog_irq != -EPROBE_DEFER)
> > + dev_err(&pdev->dev,
> > + "failed to retrieve wdog IRQ: %d\n",
> > + q6v5->wdog_irq);
> > + return q6v5->wdog_irq;
> > + }
>
> optional: Since there's the same pattern 5 times here, I wonder if we
> should abstract it out to a helper function that would print the
> error?
>
Before breaking this code out to a common function shared between the
various q6v5 drivers this was a separate helper function, but that
wasn't pretty either :/
> ...in the ideal case it would be somewhere that all Linux drivers
> could use since this is a super common pattern, but that might be a
> bit too much yak shaving...
>
Yeah I agree, it would be a nice helper but there's a bunch of variants
involved. I've added it on the "someday/maybe" list.
>
> > @@ -237,8 +260,13 @@ int qcom_q6v5_init(struct qcom_q6v5 *q6v5, struct platform_device *pdev,
> > disable_irq(q6v5->handover_irq);
> >
> > q6v5->stop_irq = platform_get_irq_byname(pdev, "stop-ack");
> > - if (q6v5->stop_irq == -EPROBE_DEFER)
> > - return -EPROBE_DEFER;
> > + if (q6v5->stop_irq < 0) {
> > + if (q6v5->stop_irq != -EPROBE_DEFER)
> > + dev_err(&pdev->dev,
> > + "failed to retrieve stop IRQ: %d\n",
> > + q6v5->stop_irq);
> > + return q6v5->stop_irq;
>
> Nitty nit that it's the "stop-ack" IRQ, not the "stop" IRQ. The error
> message below this one calls it stop-ack too so it would be ideal to
> keep it consistent between the two error messages.
>
> Reviewed-by: Douglas Anderson <dianders@chromium.org>
I applied the patch with the nit fixed and your r-b.
Thanks,
Bjorn
prev parent reply other threads:[~2018-10-10 6:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 22:25 [PATCH] remoteproc: qcom: q6v5: shore up resource probe handling Brian Norris
2018-10-09 23:34 ` Doug Anderson
2018-10-09 23:48 ` Brian Norris
2018-10-10 6:19 ` 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=20181010061920.GS12063@builder \
--to=bjorn.andersson@linaro.org \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=sibis@codeaurora.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 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).