netdev - RE: [PATCH v2 2/3] can: rcar_canfd: Fix channel specific IRQ handling for RZ/G2L

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <OS0PR01MB5922B83EE681BFAE56B420D386309@OS0PR01MB5922.jpnprd01.prod.outlook.com>
Date:   Wed, 26 Oct 2022 12:56:35 +0000
From:   Biju Das <biju.das.jz@...renesas.com>
To:     Marc Kleine-Budde <mkl@...gutronix.de>
CC:     Wolfgang Grandegger <wg@...ndegger.com>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>,
        Vincent Mailhol <mailhol.vincent@...adoo.fr>,
        Stefan Mätje <stefan.maetje@....eu>,
        Ulrich Hecht <uli+renesas@...nd.eu>,
        Fabrizio Castro <fabrizio.castro.jz@...esas.com>,
        Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@...renesas.com>,
        Oliver Hartkopp <socketcan@...tkopp.net>,
        Christophe JAILLET <christophe.jaillet@...adoo.fr>,
        "linux-can@...r.kernel.org" <linux-can@...r.kernel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Chris Paterson <Chris.Paterson2@...esas.com>,
        "linux-renesas-soc@...r.kernel.org" 
        <linux-renesas-soc@...r.kernel.org>
Subject: RE: [PATCH v2 2/3] can: rcar_canfd: Fix channel specific IRQ handling
 for RZ/G2L

Hi Marc,

Thanks for the feedback.

> Subject: Re: [PATCH v2 2/3] can: rcar_canfd: Fix channel specific IRQ
> handling for RZ/G2L
> 
> On 26.10.2022 09:34:41, Biju Das wrote:
> > > In a separate patch, please clean up these, too:
> > >
> > > | static void rcar_canfd_handle_global_err(struct
> rcar_canfd_global
> > > | *gpriv, u32 ch) static void
> > > | rcar_canfd_handle_global_receive(struct
> > > | rcar_canfd_global *gpriv, u32 ch) static void
> > > | rcar_canfd_channel_remove(struct rcar_canfd_global *gpriv, u32
> ch)
> > >
> > > Why are 2 of the above functions called "global" as they work on a
> > > specific channel? That can be streamlined, too.
> > >
> >
> > The function name is as per the hardware manual, Interrupt sources
> are
> > classified into global and channel interrupts.
> >
> > • Global interrupts (2 sources):
> > — Receive FIFO interrupt
> > — Global error interrupt
> > • Channel interrupts (3 sources/channel):
> 
> I see. Keep the functions as is.
> 
> > Maybe we could change
> > "rcar_canfd_handle_global_receive"-
> >"rcar_canfd_handle_channel_receive
> > ", as from driver point It is not global anymore?? Please let me
> know.
> 
> Never mind - the gpriv and channel numbers are needed sometimes even
> in the functions working on a single channel. Never mind. I'll take
> patches
> 1 and 2 as they are.

OK, Thanks.

Cheers,
Biju