From: Hans de Goede <hdegoede@redhat.com>
To: Stephen Boyd <swboyd@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Andy Shevchenko <andy@infradead.org>,
linux-usb <linux-usb@vger.kernel.org>,
linux-kernel@vger.kernel.org, youling 257 <youling257@gmail.com>
Subject: Problem with "driver core: platform: Add an error message to platform_get_irq*()" commit
Date: Thu, 3 Oct 2019 22:20:24 +0200 [thread overview]
Message-ID: <01e3d855-c849-ad7f-a6f8-87c806bb488b@redhat.com> (raw)
Hi all,
I've been debugging a new error printed with 5.4-rc1:
[ 25.570893] dwc3 dwc3.0.auto: IRQ peripheral not found
This is caused by the "driver core: platform: Add an error message to platform_get_irq*()"
commit.
The dwc3 driver first tries to get the IRQ by 2 different names before falling
back to the IRQ at index 0:
irq = platform_get_irq_byname(dwc3_pdev, "peripheral");
if (irq > 0)
goto out;
if (irq == -EPROBE_DEFER)
goto out;
irq = platform_get_irq_byname(dwc3_pdev, "dwc_usb3");
if (irq > 0)
goto out;
if (irq == -EPROBE_DEFER)
goto out;
irq = platform_get_irq(dwc3_pdev, 0);
Together with the mentioned commit, this is causing this new (harmless)
error message. We also have had a bug report for this:
https://bugzilla.kernel.org/show_bug.cgi?id=205037
Which I will close after this mail since the error is harmless,
still it is sorta scary looking and we should probable silence it.
The best solution I can come up with is adding a new
platform_get_irq_byname_optional mirroring platform_get_irq_optional
and using that in drivers such as the dwc3 driver.
Does anyone have a better suggestion?
Regards,
Hans
next reply other threads:[~2019-10-03 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 20:20 Hans de Goede [this message]
2019-10-03 20:25 ` Stephen Boyd
2019-10-04 12:17 ` Greg Kroah-Hartman
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=01e3d855-c849-ad7f-a6f8-87c806bb488b@redhat.com \
--to=hdegoede@redhat.com \
--cc=andy@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=swboyd@chromium.org \
--cc=youling257@gmail.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
all inboxes | Powered by JetHome®