Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20230526143615.372338-1-biju.das.jz@bp.renesas.com>
 <20230529061714.GA25984@pendragon.ideasonboard.com> <OS0PR01MB592296756992262EC6D382D0864A9@OS0PR01MB5922.jpnprd01.prod.outlook.com>
 <20230529085656.GL25984@pendragon.ideasonboard.com> <86a5xncxhc.wl-maz@kernel.org>
 <OS0PR01MB59227AF1F83A73620179CDF8864B9@OS0PR01MB5922.jpnprd01.prod.outlook.com>
In-Reply-To: <OS0PR01MB59227AF1F83A73620179CDF8864B9@OS0PR01MB5922.jpnprd01.prod.outlook.com>
From:   Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Tue, 30 May 2023 15:16:58 +0200
Message-ID: <CAMuHMdXnF87BqcxESzOjB9hSMZ0HSnqzRNXEvCXGczDj+4yPjw@mail.gmail.com>
Subject: Re: [PATCH] usb: gadget: udc: renesas_usb3: Fix RZ/V2M
 {modprobe,bind} error
To:     Biju Das <biju.das.jz@bp.renesas.com>
Cc:     Marc Zyngier <maz@kernel.org>,
        Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        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" <linux-usb@vger.kernel.org>,
        Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
        "linux-renesas-soc@vger.kernel.org" 
        <linux-renesas-soc@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
Precedence: bulk

Hi Biju,

On Tue, May 30, 2023 at 2:37 PM Biju Das <biju.das.jz@bp.renesas.com> wrote:
> > Subject: Re: [PATCH] usb: gadget: udc: renesas_usb3: Fix RZ/V2M
> > {modprobe,bind} error
> >
> > On Mon, 29 May 2023 09:56:56 +0100,
> > Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
> > >
> > > The name is just informative so I suppose it's ok. It makes me wonder,
> > > though, if the usb3drd driver shouldn't register the interrupt handler
> > > itself.
> >
> > Well, it registers it itself, but pretending to be another device.
> > Which is wrong on many levels.
>
> OK, Will register the handler in usb3drd driver and expose register/unregister handler API
> with cb function to avoid duplication of the code with renesas_usb3 driver.
>
> Basically, there will be 2 exported functions + 1 spinlock introduced in usb3drd driver
>
> USB3DRD driver register the IRQ handler
>
> Probe/remove from renesas_usb3 driver register/unregister the cb function. Whenever there is drd irq
> cb function will be called.

Please don't make it more complicated: if the parent device does not
use that interrupt, there is no need to move its handling to the parent
device driver.

Your patch looks fine to me, just replace the second ddata->dev, too.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds