From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: "Wolfgang Grandegger" <wg@grandegger.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Vincent Mailhol" <mailhol.vincent@wanadoo.fr>,
"Stefan Mätje" <stefan.maetje@esd.eu>,
"Ulrich Hecht" <uli+renesas@fpond.eu>,
"Fabrizio Castro" <fabrizio.castro.jz@renesas.com>,
"Lad Prabhakar" <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"Oliver Hartkopp" <socketcan@hartkopp.net>,
"Christophe JAILLET" <christophe.jaillet@wanadoo.fr>,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Chris Paterson" <Chris.Paterson2@renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 2/3] can: rcar_canfd: Fix channel specific IRQ handling for RZ/G2L
Date: Wed, 26 Oct 2022 09:36:08 +0200 [thread overview]
Message-ID: <20221026073608.7h47b2axcayakfnn@pengutronix.de> (raw)
In-Reply-To: <20221025155657.1426948-3-biju.das.jz@bp.renesas.com>
[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]
On 25.10.2022 16:56:56, Biju Das wrote:
> RZ/G2L has separate channel specific IRQs for transmit and error
> interrupt. But the IRQ handler, process the code for both channels
> even if there is no interrupt occurred on one of the channels.
>
> This patch fixes the issue by passing channel specific context
> parameter instead of global one for irq register and on irq handler,
> it just handles the channel which is triggered the interrupt.
Please clean up signatures of the IRQ handlers you touch, it's a little
mess. Change:
| rcar_canfd_handle_channel_tx(struct rcar_canfd_global *gpriv, u32 ch)
to:
| rcar_canfd_handle_channel_tx(struct rcar_canfd_channel *priv)
Same for:
| static void rcar_canfd_handle_channel_err(struct rcar_canfd_global *gpriv, u32 ch)
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.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-10-26 7:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 15:56 [PATCH v2 0/3] R-Car CANFD fixes Biju Das
2022-10-25 15:56 ` [PATCH v2 1/3] can: rcar_canfd: Fix IRQ storm on global fifo receive Biju Das
2022-10-25 15:56 ` [PATCH v2 2/3] can: rcar_canfd: Fix channel specific IRQ handling for RZ/G2L Biju Das
2022-10-26 7:36 ` Marc Kleine-Budde [this message]
2022-10-26 9:34 ` Biju Das
2022-10-26 12:34 ` Marc Kleine-Budde
2022-10-26 12:56 ` Biju Das
2022-10-25 15:56 ` [PATCH v2 3/3] can: rcar_canfd: Use devm_reset_control_get_optional_exclusive Biju Das
2022-10-26 7:40 ` Geert Uytterhoeven
2022-10-26 7:41 ` Marc Kleine-Budde
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=20221026073608.7h47b2axcayakfnn@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=socketcan@hartkopp.net \
--cc=stefan.maetje@esd.eu \
--cc=uli+renesas@fpond.eu \
--cc=wg@grandegger.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