All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: nobuhiro1.iwamatsu@toshiba.co.jp
Cc: cip-dev@lists.cip-project.org, biju.das.jz@bp.renesas.com,
	pavel@denx.de, fabrizio.castro.jz@renesas.com
Subject: Re: [cip-dev] [PATCH 5.10.y-cip] usb: gadget: udc: renesas_usb3: Fix RZ/V2M {modprobe,bind} error
Date: Fri, 7 Jul 2023 17:35:51 +0200	[thread overview]
Message-ID: <ZKgw16/ePAKx/1FB@duo.ucw.cz> (raw)
In-Reply-To: <TYWPR01MB94208D921A8950BC0A3CD6FD922CA@TYWPR01MB9420.jpnprd01.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]

Hi!

> > > 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
> > >
> > > The reason is, it is trying to register an interrupt handler for the same IRQ
> > twice.
> > > The devm_request_irq() was called with the parent device.
> > > So the interrupt handler won't be unregistered when the usb3-peri
> > > device is unbound.
> > >
> > > Fix this issue by replacing "parent dev"->"dev" as the irq resource is
> > > managed by this driver.

> > I reviewed this series. Looks fine to me.
> > I can apply, if there are no comments and issues.
> > 
> > Test:
> > https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/919946031
> > Reviewed-by: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
> > 
> Applied, thanks.

Looks ok to me, too.

Thanks and best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2023-07-07 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03 13:21 [PATCH 5.10.y-cip] usb: gadget: udc: renesas_usb3: Fix RZ/V2M {modprobe,bind} error Biju Das
2023-07-04  4:34 ` nobuhiro1.iwamatsu
     [not found] ` <176E900B4C685A01.1228@lists.cip-project.org>
2023-07-06  0:19   ` [cip-dev] " nobuhiro1.iwamatsu
2023-07-07 15:35     ` Pavel Machek [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=ZKgw16/ePAKx/1FB@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=fabrizio.castro.jz@renesas.com \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.