From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Arun Muthusamy <arun.muthusamy@gaisler.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
mailhol@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-can@vger.kernel.org
Subject: Re: [PATCH v3 00/15] can: grcan: Enhance driver with CANFD Support and Improvemens
Date: Fri, 23 Jan 2026 15:30:22 +0100 [thread overview]
Message-ID: <20260123-evasive-chirpy-bug-6ac9d8-mkl@pengutronix.de> (raw)
In-Reply-To: <20260122121038.7910-1-arun.muthusamy@gaisler.com>
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]
On 22.01.2026 13:10:23, Arun Muthusamy wrote:
> This patch series updates the GRCAN driver to support the GRCANFD core
> from the GRLIB IP core library.
>
> In addition to GRCANFD support, the updates include enhancements for
> compatibility with NOEL-V (RISC-V) systems, such as matching drivers
> using the 'compatible' identifier and adding support for reading clock
> frequency via the common clock framework where available. The series
> also includes improvements like functions for configuring
> nominal bit-timing and optimizations for DMA operations.
>
> This series also updates the driver documentation and bindings.
> The old text binding is converted to YAML, a new vendor prefix
> is added to reflect the updated ownership and an entry for the
> driver is added to the MAINTAINERS file.
The order of patches is strange.
In #12 you claim to support CAN-FD, but actual support is added in
#13...15.
The kernel should be functional on every commit. Please change the order
of patches, that CAN-FD support can only be enabled if the driver really
supports it.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung Nürnberg | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-01-23 14:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 12:10 Arun Muthusamy
2026-01-22 12:10 ` [PATCH v3 01/15] dt-bindings: Add vendor prefix for Frontgrade Gaisler AB Arun Muthusamy
2026-01-22 12:44 ` Krzysztof Kozlowski
2026-01-22 12:10 ` [PATCH v3 02/15] net: can: Convert gaisler,grcan to DT schema Arun Muthusamy
2026-01-22 12:10 ` [PATCH v3 03/15] MAINTAINERS: Add maintainers for GRCAN CAN network driver Arun Muthusamy
2026-01-22 12:10 ` [PATCH v3 04/15] can: grcan: Add clock handling Arun Muthusamy
2026-01-23 13:44 ` Marc Kleine-Budde
2026-01-27 13:27 ` Arun Muthusamy
2026-01-22 12:10 ` [PATCH v3 05/15] can: grcan: Replace bit timing macros with literal values Arun Muthusamy
2026-01-22 12:10 ` [PATCH v3 06/15] can: grcan: Simplify timing configuration Arun Muthusamy
2026-01-22 12:10 ` [PATCH v3 07/15] can: grcan: add FD capability detection and nominal bit-timing Arun Muthusamy
2026-01-23 13:52 ` Marc Kleine-Budde
2026-01-22 12:10 ` [PATCH v3 08/15] can: grcan: optimize DMA by 32-bit accesses Arun Muthusamy
2026-01-22 12:10 ` [PATCH v3 09/15] can: grcan: set DMA mask for GRCAN and GRCANFD to 32-bit Arun Muthusamy
2026-01-22 12:10 ` [PATCH v3 10/15] can: grcan: Add saving and restoring of CAN FD baud-rate registers Arun Muthusamy
2026-01-23 14:00 ` Marc Kleine-Budde
2026-01-28 8:35 ` Arun Muthusamy
2026-01-22 12:10 ` [PATCH v3 11/15] can: grcan: Reserve space between cap and next register to align with address layout Arun Muthusamy
2026-01-22 12:10 ` [PATCH v3 12/15] can: grcan: Advertise CANFD capability Arun Muthusamy
2026-01-22 12:10 ` [PATCH v3 13/15] can: grcan: Add CANFD TX support alongside legacy CAN Arun Muthusamy
2026-01-23 14:25 ` Marc Kleine-Budde
2026-01-27 14:06 ` Arun Muthusamy
2026-01-27 14:12 ` Marc Kleine-Budde
2026-01-27 14:17 ` Arun Muthusamy
2026-01-27 14:18 ` Marc Kleine-Budde
2026-01-22 12:10 ` [PATCH v3 14/15] can: grcan: Add CANFD RX " Arun Muthusamy
2026-01-22 12:10 ` [PATCH v3 15/15] can: grcan: Update echo skb handling to match variable length CANFD frame Arun Muthusamy
2026-01-23 14:12 ` Marc Kleine-Budde
2026-01-23 14:17 ` Marc Kleine-Budde
2026-01-28 8:14 ` Arun Muthusamy
2026-01-23 14:30 ` Marc Kleine-Budde [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=20260123-evasive-chirpy-bug-6ac9d8-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=arun.muthusamy@gaisler.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®