From: Rob Herring <robh@kernel.org>
To: Arun Muthusamy <arun.muthusamy@gaisler.com>
Cc: krzk+dt@kernel.org, conor+dt@kernel.org, mkl@pengutronix.de,
mailhol@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-can@vger.kernel.org
Subject: Re: [PATCH v2 02/10] dt-bindings: net: can: grcan: Convert GRCAN CAN controllers binding from txt to YAML
Date: Mon, 29 Dec 2025 20:19:24 -0600 [thread overview]
Message-ID: <20251230021924.GA3176103-robh@kernel.org> (raw)
In-Reply-To: <20251223105604.12675-3-arun.muthusamy@gaisler.com>
On Tue, Dec 23, 2025 at 11:55:56AM +0100, Arun Muthusamy wrote:
> Migrate device tree bindings for Gaisler GRCAN, GRHCAN
> and GRCANFD CAN controllers from a text format to YAML format.
A more concise subject would be:
net: can: Convert gaisler,grcan to DT schema
Otherwise,
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
>
> 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>
> ---
> .../bindings/net/can/gaisler,grcan.yaml | 62 +++++++++++++++++++
> .../devicetree/bindings/net/can/grcan.txt | 28 ---------
> 2 files changed, 62 insertions(+), 28 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/net/can/gaisler,grcan.yaml
> delete mode 100644 Documentation/devicetree/bindings/net/can/grcan.txt
next prev parent reply other threads:[~2025-12-30 2:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 10:55 [PATCH v2 00/10] can: grcan: Enhance driver with CANFD Support and Improvements Arun Muthusamy
2025-12-23 10:55 ` [PATCH v2 01/10] dt-bindings: Add vendor prefix for Frontgrade Gaisler AB Arun Muthusamy
2025-12-27 12:31 ` Krzysztof Kozlowski
2025-12-23 10:55 ` [PATCH v2 02/10] dt-bindings: net: can: grcan: Convert GRCAN CAN controllers binding from txt to YAML Arun Muthusamy
2025-12-24 2:29 ` kernel test robot
2025-12-30 2:19 ` Rob Herring [this message]
2025-12-23 10:55 ` [PATCH v2 03/10] MAINTAINERS: Add maintainers for GRCAN CAN network driver Arun Muthusamy
2025-12-23 10:55 ` [PATCH v2 04/10] can: grcan: Add clock handling Arun Muthusamy
2025-12-23 10:55 ` [PATCH v2 05/10] can: grcan: add FD capability detection and nominal bit-timing Arun Muthusamy
2025-12-23 20:51 ` Vincent Mailhol
2025-12-23 10:56 ` [PATCH v2 06/10] can: grcan: optimize DMA by 32-bit accesses Arun Muthusamy
2025-12-23 20:40 ` Vincent Mailhol
2025-12-23 10:56 ` [PATCH v2 07/10] can: grcan: set DMA mask for GRCAN and GRCANFD to 32-bit Arun Muthusamy
2025-12-23 10:56 ` [PATCH v2 08/10] can: grcan: Add saving and restoring of CAN FD baud-rate registers Arun Muthusamy
2025-12-23 10:56 ` [PATCH v2 09/10] can: grcan: Reserve space between cap and next register to align with address layout Arun Muthusamy
2025-12-23 10:56 ` [PATCH v2 10/10] can: grcan: Add CANFD support alongside legacy CAN Arun Muthusamy
2025-12-23 21:09 ` Vincent Mailhol
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=20251230021924.GA3176103-robh@kernel.org \
--to=robh@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 \
/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;
as well as URLs for NNTP newsgroup(s).