From: Krzysztof Kozlowski <krzk@kernel.org>
To: Arun Muthusamy <arun.muthusamy@gaisler.com>
Cc: robh@kernel.org, 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 02/10] dt-bindings: net: can: grcan: Convert GRCAN CAN controllers binding from txt to YAML
Date: Thu, 18 Dec 2025 11:12:40 +0100 [thread overview]
Message-ID: <b7fdd6d7-fd56-4e3a-84da-191411f9edd6@kernel.org> (raw)
In-Reply-To: <13d562aa-3425-4753-a78f-dd268dd78794@gaisler.com>
On 11/12/2025 11:11, Arun Muthusamy wrote:
> Hi Krzysztof,
>
> Thank you for your thorough review. I’d like to clarify a few points
> regarding the DT binding and get your guidance.
>
> On 11/18/25 12:01, Krzysztof Kozlowski wrote:
>> On 18/11/2025 10:21, Arun Muthusamy wrote:
>>> + Fallback on node name matching for systems that don't provide compatible.
>>> + enum:
>>> + - GAISLER_GRCAN
>>> + - 01_03d
>>> + - GAISLER_GRHCAN
>>> + - "01_034"
>> This does not really work. Are you really defining here "name" property?
>
> The driver supports two of the platforms which are LEON and NOEL
I don't care much about driver. Please describe here hardware.
> platforms. PROM-based *LEON* systems identify uses the "node name"
> property, while DTS based *NOEL* systems use proper "|compatible"|strings. On LEON (SPARC32), AMBA Plug & Play information creates the DT
> properties, and drivers historically match devices based on node names.
> To reflect this, I updated the $nodename pattern to support LEON-style
> node names: properties:
> $nodename:
> pattern: "^(GAISLER_GRCAN|01_03d|GAISLER_GRHCAN|01_034)$" I’d
> appreciate any suggestions on the preferred way to describe this node
> name for PROM-based LEON.
>
>>> +
>>> + reg:
>>> + maxItems: 1
>>> +
>>> + interrupts:
>>> + maxItems: 1
>>> +
>>> + clocks:
>>> + maxItems: 1
>>> +
>>> + freq:
>>> + $ref: /schemas/types.yaml#/definitions/uint32
>>> + description: |
>>> + Frequency of the external oscillator clock in Hz (the frequency of the
>>> + amba bus in the ordinary case).
>>> + This property should be used by systems that utilize the common clock
>>> + framework is not supported.
>> Missing systemid. Your commit msg must explain any changes done to the
>> binding during conversion.
>
> The driver now reads systemid directly from /ambapp0, so the property no
> longer needs to be defined in the DTS. The previous documentation was
> outdated and should have been updated after commit:
> 1e93ed26acf0 ("can: grcan: grcan_probe(): fix broken system id check for
> errata workaround needs").
Read again what I wrote.
>
>>> + - reg
>>> + - interrupts
>> Where is freq? It was required in the old binding. Again, you need to
>> explain the changes.
>
> LEON: relies on the freq property
> NOEL: uses a standard clocks binding
> Because of this dual approach, the freq property is no longer required
> in the DTS binding itself as theAMBA Plug & Play creates the DT properties.
Please read my comment carefully: you need to explain the changes. But
not to me, to everyone in the commit msg.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-18 10:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 9:21 [PATCH 00/10] can: grcan: Enhance driver with CANFD Support and Improvements Arun Muthusamy
2025-11-18 9:21 ` [PATCH 01/10] dt-bindings: Add vendor prefix for Frontgrade Gaisler AB Arun Muthusamy
2025-11-18 10:56 ` Krzysztof Kozlowski
2025-11-18 9:21 ` [PATCH 02/10] dt-bindings: net: can: grcan: Convert GRCAN CAN controllers binding from txt to YAML Arun Muthusamy
2025-11-18 11:01 ` Krzysztof Kozlowski
2025-11-24 9:37 ` Arun Muthusamy
2025-11-24 11:28 ` Krzysztof Kozlowski
2025-12-11 10:11 ` Arun Muthusamy
2025-12-18 10:12 ` Krzysztof Kozlowski [this message]
[not found] ` <0c4a38e1-29e9-4892-ad99-539dd889d4a8@gaisler.com>
2025-12-18 10:10 ` Krzysztof Kozlowski
2025-11-18 9:21 ` [PATCH 03/10] MAINTAINERS: Add entry for GRCAN CAN network driver Arun Muthusamy
2025-11-18 9:21 ` [PATCH 04/10] can: grcan: Add clock handling Arun Muthusamy
2025-11-18 11:01 ` Krzysztof Kozlowski
2025-11-24 9:46 ` Arun Muthusamy
2025-11-24 11:10 ` Krzysztof Kozlowski
2025-11-18 9:21 ` [PATCH 05/10] can: grcan: add FD capability detection and nominal bit-timing Arun Muthusamy
2025-11-21 10:52 ` Marc Kleine-Budde
2025-11-18 9:21 ` [PATCH 06/10] can: grcan: optimize DMA by 32-bit accesses Arun Muthusamy
2025-11-21 11:00 ` Marc Kleine-Budde
2025-11-18 9:21 ` [PATCH 07/10] can: grcan: set DMA mask for GRCAN and GRCANFD to 32-bit Arun Muthusamy
2025-11-21 12:46 ` Marc Kleine-Budde
2025-11-18 9:21 ` [PATCH 08/10] can: grcan: Add saving and restoring of CAN FD baud-rate registers Arun Muthusamy
2025-11-21 12:50 ` Marc Kleine-Budde
2025-12-11 9:13 ` Arun Muthusamy
2025-12-11 11:37 ` Marc Kleine-Budde
2025-11-18 9:21 ` [PATCH 09/10] can: grcan: Reserve space between cap and next register to align with address layout Arun Muthusamy
2025-11-18 9:21 ` [PATCH 10/10] can: grcan: Add CANFD support alongside legacy CAN Arun Muthusamy
2025-11-21 13:03 ` 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=b7fdd6d7-fd56-4e3a-84da-191411f9edd6@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;
as well as URLs for NNTP newsgroup(s).