From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Zheng Wang <zyytlz.wz@163.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-usb@vger.kernel.org,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: udc: renesas_usb3: Fix RZ/V2M {modprobe,bind} error
Date: Mon, 29 May 2023 09:17:14 +0300 [thread overview]
Message-ID: <20230529061714.GA25984@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20230526143615.372338-1-biju.das.jz@bp.renesas.com>
Hi Biju,
Thank you for the patch.
On Fri, May 26, 2023 at 03:36:15PM +0100, Biju Das wrote:
> Currently {modprobe, bind} after {rmmod, unbind} results in probe failure.
>
> genirq: Flags mismatch irq 22. 00000004 (85070400.usb3drd) vs. 00000004 (85070400.usb3drd)
> renesas_usb3: probe of 85070000.usb3peri failed with error -16
>
> Fix this issue by replacing "parent dev"->"dev" as the irq resource
> is managed by this driver.
If the dev pointer passed to devm_request_irq() is not the correct one,
how does it work the first time the driver is loaded ?
> Fixes: 9cad72dfc556 ("usb: gadget: Add support for RZ/V2M USB3DRD driver"
There's a missing ')' at the end of the line.
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
> drivers/usb/gadget/udc/renesas_usb3.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/gadget/udc/renesas_usb3.c b/drivers/usb/gadget/udc/renesas_usb3.c
> index aac8bc185afa..4a37b2e4b9b3 100644
> --- a/drivers/usb/gadget/udc/renesas_usb3.c
> +++ b/drivers/usb/gadget/udc/renesas_usb3.c
> @@ -2877,7 +2877,7 @@ static int renesas_usb3_probe(struct platform_device *pdev)
> struct rzv2m_usb3drd *ddata = dev_get_drvdata(pdev->dev.parent);
>
> usb3->drd_reg = ddata->reg;
> - ret = devm_request_irq(ddata->dev, ddata->drd_irq,
> + ret = devm_request_irq(&pdev->dev, ddata->drd_irq,
> renesas_usb3_otg_irq, 0,
> dev_name(ddata->dev), usb3);
Shouldn't you use dev_name(&pdev->dev) too ?
> if (ret < 0)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2023-05-29 6:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 14:36 [PATCH] usb: gadget: udc: renesas_usb3: Fix RZ/V2M {modprobe,bind} error Biju Das
2023-05-29 6:17 ` Laurent Pinchart [this message]
2023-05-29 8:42 ` Biju Das
2023-05-29 8:56 ` Laurent Pinchart
2023-05-29 9:12 ` Marc Zyngier
2023-05-30 12:37 ` Biju Das
2023-05-30 13:16 ` Geert Uytterhoeven
2023-05-30 13:47 ` Biju Das
2023-05-29 9:09 ` Marc Zyngier
2023-05-29 9:39 ` Biju Das
2023-05-29 9:46 ` Laurent Pinchart
2023-05-29 9:59 ` Biju Das
2023-05-29 9:56 ` Marc Zyngier
2023-05-29 10:03 ` Biju Das
2023-05-29 11:15 ` Marc Zyngier
2023-05-29 13:20 ` Biju Das
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=20230529061714.GA25984@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
--cc=zyytlz.wz@163.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