Linux CAN drivers development
 help / color / mirror / Atom feed
From: <Charan.Pedumuru@microchip.com>
To: <mkl@pengutronix.de>
Cc: <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] dt-bindings: net: can: atmel: Convert to json schema
Date: Fri, 20 Sep 2024 04:51:57 +0000	[thread overview]
Message-ID: <d9987295-74eb-4795-8517-379249cd7626@microchip.com> (raw)
In-Reply-To: <20240912-literate-caped-mandrill-4c0c9d-mkl@pengutronix.de>

On 12/09/24 13:05, Marc Kleine-Budde wrote:
> On 12.09.2024 11:19:16, Charan Pedumuru wrote:
>> Convert atmel-can documentation to yaml format
>>
>> Signed-off-by: Charan Pedumuru<charan.pedumuru@microchip.com>
>> ---
>>   .../bindings/net/can/atmel,at91sam9263-can.yaml    | 67 ++++++++++++++++++++++
>>   .../devicetree/bindings/net/can/atmel-can.txt      | 15 -----
>>   2 files changed, 67 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..269af4c993a7
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/net/can/atmel,at91sam9263-can.yaml
>> @@ -0,0 +1,67 @@
>> +# 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: Atmel CAN Controller
>> +
>> +maintainers:
>> +  - Nicolas Ferre<nicolas.ferre@microchip.com>
>> +
>> +properties:
>> +  compatible:
>> +    oneOf:
>> +      - enum:
>> +          - atmel,at91sam9263-can
>> +          - atmel,at91sam9x5-can
>> +          - microchip,sam9x60-can
> The driver doesn't have a compatible for "microchip,sam9x60-can".
Yes, I will remove it.
>
>> +      - items:
>> +          - enum:
>> +              - microchip,sam9x60-can
>> +          - const: atmel,at91sam9x5-can
>> +
>> +  reg:
>> +    maxItems: 1
>> +
>> +  interrupts:
>> +    maxItems: 1
>> +
>> +  clocks:
>> +    maxItems: 1
>> +
>> +  clock-names:
>> +    items:
>> +      - const: can_clk
>> +
>> +required:
>> +  - compatible
>> +  - reg
>> +  - interrupts
>> +
>> +allOf:
>> +  - $ref: can-controller.yaml#
>> +  - if:
>> +      properties:
>> +        compatible:
>> +          contains:
>> +            enum:
>> +              - microchip,sam9x60-can
>> +    then:
>> +      required:
>> +        - compatible
>> +        - reg
>> +        - interrupts
>> +        - clocks
>> +        - clock-names
> AFAICS clock-names is required for all compatibles.
In our case only sam9x60 is using clock-names property.
>
>> +
>> +unevaluatedProperties: false
>> +
>> +examples:
>> +  - |
>> +    #include <dt-bindings/interrupt-controller/irq.h>
>> +    can0: can@f000c000 {
> I think unused labels should be removed.
Ok, I will remove the labels in next revision. Thanks.
>
>> +          compatible = "atmel,at91sam9x5-can";
>> +          reg = <0xf000c000 0x300>;
>> +          interrupts = <30 IRQ_TYPE_LEVEL_HIGH 3>;
>> +    };
>> diff --git a/Documentation/devicetree/bindings/net/can/atmel-can.txt b/Documentation/devicetree/bindings/net/can/atmel-can.txt
>> deleted file mode 100644
>> index 218a3b3eb27e..000000000000
>> --- a/Documentation/devicetree/bindings/net/can/atmel-can.txt
>> +++ /dev/null
>> @@ -1,15 +0,0 @@
>> -* AT91 CAN *
>> -
>> -Required properties:
>> -  - compatible: Should be "atmel,at91sam9263-can", "atmel,at91sam9x5-can" or
>> -    "microchip,sam9x60-can"
>> -  - reg: Should contain CAN controller registers location and length
>> -  - interrupts: Should contain IRQ line for the CAN controller
>> -
>> -Example:
>> -
>> -	can0: can@f000c000 {
>> -		compatible = "atmel,at91sam9x5-can";
>> -		reg = <0xf000c000 0x300>;
>> -		interrupts = <40 4 5>
>> -	};
>>
>> ---
>> base-commit: 32ffa5373540a8d1c06619f52d019c6cdc948bb4
>> change-id: 20240912-can-8eb7f8e7566d
>>
>> Best regards,
>> -- 
>> Charan Pedumuru<charan.pedumuru@microchip.com>
>>
>>
>>
> Marc

-- 
Best Regards,
Charan.


  reply	other threads:[~2024-09-20  4:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12  5:49 [PATCH] dt-bindings: net: can: atmel: Convert to json schema Charan Pedumuru
2024-09-12  6:24 ` Dharma.B
2024-09-12  6:36 ` Conor Dooley
2024-09-12  7:35 ` Marc Kleine-Budde
2024-09-20  4:51   ` Charan.Pedumuru [this message]
2024-09-23 10:57     ` Marc Kleine-Budde
2024-09-30  4:07       ` Charan.Pedumuru

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=d9987295-74eb-4795-8517-379249cd7626@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=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