From: <Charan.Pedumuru@microchip.com>
To: <krzk@kernel.org>
Cc: <mkl@pengutronix.de>, <mailhol.vincent@wanadoo.fr>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <Nicolas.Ferre@microchip.com>,
<alexandre.belloni@bootlin.com>, <claudiu.beznea@tuxon.dev>,
<linux-can@vger.kernel.org>, <netdev@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: net: can: atmel: Convert to json schema
Date: Wed, 13 Nov 2024 05:30:53 +0000 [thread overview]
Message-ID: <cd3a9342-3863-4a81-9b09-db7b8da1d561@microchip.com> (raw)
In-Reply-To: <xykmnsibdts7u73yu7b2vn3w55wx7puqo2nwhsji57th7lemym@f4l3ccxpevo4>
On 03/10/24 14:04, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Thu, Oct 03, 2024 at 10:37:03AM +0530, Charan Pedumuru wrote:
>> Convert atmel-can documentation to yaml format
>>
>> Signed-off-by: Charan Pedumuru <charan.pedumuru@microchip.com>
>> ---
>> Changes in v2:
>> - Renamed the title to "Microchip AT91 CAN controller"
>> - Removed the unnecessary labels and add clock properties to examples
>> - Removed if condition statements and made clock properties as default required properties
>> - Link to v1: https://lore.kernel.org/r/20240912-can-v1-1-c5651b1809bb@microchip.com
>> ---
>> .../bindings/net/can/atmel,at91sam9263-can.yaml | 58 ++++++++++++++++++++++
>> .../devicetree/bindings/net/can/atmel-can.txt | 15 ------
>> 2 files changed, 58 insertions(+), 15 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/net/can/atmel,at91sam9263-can.yaml b/Documentation/devicetree/bindings/net/can/atmel,at91sam9263-can.yaml
>> new file mode 100644
>> index 000000000000..c818c01a718b
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/net/can/atmel,at91sam9263-can.yaml
>> @@ -0,0 +1,58 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/net/can/atmel,at91sam9263-can.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Microchip AT91 CAN Controller
>> +
>> +maintainers:
>> + - Nicolas Ferre <nicolas.ferre@microchip.com>
>> +
>> +allOf:
>> + - $ref: can-controller.yaml#
>> +
>> +properties:
>> + compatible:
>> + oneOf:
>> + - enum:
>> + - atmel,at91sam9263-can
>> + - atmel,at91sam9x5-can
>> + - items:
>> + - enum:
>> + - microchip,sam9x60-can
>> + - const: atmel,at91sam9x5-can
> That is not what old binding said.
Apologies for the late reply, the driver doesn't have compatible with
"microchip,sam9x60-can",
so I made "atmel,at91sam9x5-can" as fallback driver
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + interrupts:
>> + maxItems: 1
>> +
>> + clocks:
>> + maxItems: 1
>> +
>> + clock-names:
>> + items:
>> + - const: can_clk
> These are new...
These were already defined in the previous revision.
>
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - interrupts
>> + - clocks
>> + - clock-names
> Here the same. Each change to the binding should be explained (answer
> to the: why) in commit msg.
Sure, I will include the reason for changes in commit message for the
next revision.
>
>> +
>> +unevaluatedProperties: false
> Best regards,
> Krzysztof
>
--
Best Regards,
Charan.
next prev parent reply other threads:[~2024-11-13 5:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 5:07 [PATCH v2] dt-bindings: net: can: atmel: Convert to json schema Charan Pedumuru
2024-10-03 8:34 ` Krzysztof Kozlowski
2024-11-13 5:30 ` Charan.Pedumuru [this message]
2024-11-14 9:29 ` Marc Kleine-Budde
2024-11-19 9:10 ` Krzysztof Kozlowski
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=cd3a9342-3863-4a81-9b09-db7b8da1d561@microchip.com \
--to=charan.pedumuru@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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).