[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1a837bec-8658-3200-edff-76809de3fae6@linaro.org>
Date: Wed, 8 Mar 2023 15:34:46 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: dev@...henker.ch, devicetree@...r.kernel.org,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>
Cc: NXP Linux Team <linux-imx@....com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Frank Rowand <frowand.list@...il.com>,
linux-arm-kernel@...ts.infradead.org,
Fabio Estevam <festevam@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 17/25] arm64: dts: colibri-imx8x: eval: Add spi-to-can
On 08/03/2023 14:43, Philippe Schenker wrote:
>>> + mcp2515: can@0 {
>>> + compatible = "microchip,mcp2515";
>>> + reg = <0>;
>>> + interrupt-parent = <&lsio_gpio3>;
>>> + interrupts = <13 IRQ_TYPE_EDGE_FALLING>;
>>> + pinctrl-0 = <&pinctrl_can_int>;
>>> + pinctrl-names = "default";
>>> + clocks = <&clk16m>;
>>
>> You just sorted all nodes in previous patches and add something
>> unsorted? What is then the style of order? Random name?
>
> My logic behind this one is
>
> 1. compatible property
> 2. reg property
> 3. standard properties
> - first interrupt
> - then pinctrl
> 4. specific properties
> - again alphabetically: clocks, spi-max-frequency
clocks and spi-max-frequency are standard properties.
BTW, what is a specific property?
Best regards,
Krzysztof
Powered by blists - more mailing lists