From: Claudiu Beznea <claudiu.beznea@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Vincent Mailhol <mailhol@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>
Cc: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Tu Nguyen <tu.nguyen.xg@renesas.com>,
linux-can@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>
Subject: Re: [PATCH v3 2/3] can: rcar_canfd: Derive max_channels from the device tree
Date: Fri, 25 Sep 2026 11:44:42 +0300 [thread overview]
Message-ID: <35b1f45f-28e2-4e36-89e8-64b016596a6b@kernel.org> (raw)
In-Reply-To: <20260925082134.146015-3-biju.das.jz@bp.renesas.com>
On 9/25/26 11:21, Biju Das wrote:
> The maximum number of channels is currently hardcoded per SoC in
> struct rcar_canfd_hw_info. Since the DT describes the channels as
> child nodes of the controller, the count can be obtained at probe time
> with of_get_child_count() instead.
>
> Drop max_channels from struct rcar_canfd_hw_info and store the value
> in struct rcar_canfd_global, so it no longer needs to be maintained
> for each SoC variant. Update all for_each_set_bit() users over
> channels_mask to use gpriv->max_channels.
>
> No functional change.
>
> Signed-off-by: Biju Das<biju.das.jz@bp.renesas.com>
Reviewed-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
next prev parent reply other threads:[~2026-09-25 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 8:21 [PATCH v3 0/3] Add support for Renesas RZ/G3L CANFD Biju Das
2026-09-25 8:21 ` [PATCH v3 1/3] dt-bindings: can: renesas,rcar-canfd: Document RZ/G3L SoC Biju Das
2026-10-01 6:03 ` Krzysztof Kozlowski
2026-09-25 8:21 ` [PATCH v3 2/3] can: rcar_canfd: Derive max_channels from the device tree Biju Das
2026-09-25 8:39 ` Geert Uytterhoeven
2026-09-25 8:44 ` Claudiu Beznea [this message]
2026-09-25 8:21 ` [PATCH v3 3/3] can: rcar_canfd: Add support for Renesas RZ/G3L Biju Das
2026-09-25 8:46 ` Claudiu Beznea
2026-09-29 14:23 ` [PATCH v3 0/3] Add support for Renesas RZ/G3L CANFD Marc Kleine-Budde
2026-09-29 14:25 ` 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=35b1f45f-28e2-4e36-89e8-64b016596a6b@kernel.org \
--to=claudiu.beznea@kernel.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-can@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=tu.nguyen.xg@renesas.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