From: Krzysztof Kozlowski <krzk@kernel.org>
To: Arun Muthusamy <arun.muthusamy@gaisler.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
mkl@pengutronix.de, mailhol@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-can@vger.kernel.org
Subject: Re: [PATCH v5 02/16] net: can: Convert gaisler,grcan to DT schema
Date: Mon, 16 Feb 2026 15:59:44 +0100 [thread overview]
Message-ID: <20fb1a19-7b1c-4520-91fc-50e21589b9ed@kernel.org> (raw)
In-Reply-To: <20260216135344.23246-3-arun.muthusamy@gaisler.com>
On 16/02/2026 14:53, Arun Muthusamy wrote:
> Migrate device tree bindings for Gaisler GRCAN, GRHCAN
> and GRCANFD CAN controllers from a text format to YAML format.
>
> Additional changes:
> - Remove stale systemid property
> removed in commit 1e93ed26acf0 ("can: grcan: grcan_probe():
> fix broken system id check for errata workaround needs")
> - Make freq optional
> - Add clocks
> - Add compatible
> - Add example
>
> Signed-off-by: Arun Muthusamy <arun.muthusamy@gaisler.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
> ---
> .../bindings/net/can/gaisler,grcan.yaml | 62 +++++++++++++++++++
> .../devicetree/bindings/net/can/grcan.txt | 28 ---------
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching. For bindings, the preferred subjects are
explained here:
https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-16 14:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 13:53 [PATCH v5 00/16] can: grcan: Enhance driver with CANFD Support and Improvements Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 01/16] dt-bindings: Add vendor prefix for Frontgrade Gaisler AB Arun Muthusamy
2026-02-16 14:53 ` Krzysztof Kozlowski
2026-02-16 13:53 ` [PATCH v5 02/16] net: can: Convert gaisler,grcan to DT schema Arun Muthusamy
2026-02-16 14:59 ` Krzysztof Kozlowski [this message]
2026-02-16 13:53 ` [PATCH v5 03/16] MAINTAINERS: Add maintainers for GRCAN CAN network driver Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 04/16] can: grcan: Add clock handling Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 05/16] can: grcan: Replace bit timing macros with literal values Arun Muthusamy
2026-02-16 15:01 ` Krzysztof Kozlowski
2026-03-05 15:43 ` Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 06/16] can: grcan: Simplify timing configuration Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 07/16] can: grcan: add FD capability detection and nominal bit-timing Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 08/16] can: grcan: optimize DMA by 32-bit accesses Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 09/16] can: grcan: set DMA mask for GRCAN and GRCANFD to 32-bit Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 10/16] can: grcan: Add saving and restoring of CAN FD baud-rate registers Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 11/16] can: grcan: Reserve space between cap and next register to align with address layout Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 12/16] can: grcan: Refactor GRCAN DMA buffer to use structured memory layout Arun Muthusamy
2026-02-22 15:46 ` Vincent Mailhol
2026-02-16 13:53 ` [PATCH v5 13/16] can: grcan: Add CANFD TX support alongside legacy CAN Arun Muthusamy
2026-02-22 15:28 ` Vincent Mailhol
2026-02-16 13:53 ` [PATCH v5 14/16] can: grcan: Add CANFD RX " Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 15/16] can: grcan: Update echo skb handling to match variable length CANFD frame Arun Muthusamy
2026-02-16 13:53 ` [PATCH v5 16/16] can: grcan: Advertise CANFD capability Arun Muthusamy
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=20fb1a19-7b1c-4520-91fc-50e21589b9ed@kernel.org \
--to=krzk@kernel.org \
--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=mkl@pengutronix.de \
--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®