devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andrei Simion <andrei.simion@microchip.com>,
	claudiu.beznea@tuxon.dev, nicolas.ferre@microchip.com,
	alexandre.belloni@bootlin.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, peda@axentia.se
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	cristian.birsan@microchip.com
Subject: Re: [PATCH 4/5] ARM: dts: microchip: Rename the usb node
Date: Wed, 14 Aug 2024 15:22:34 +0200	[thread overview]
Message-ID: <29e5fada-8f8a-4cc0-b1d0-14396f6736a6@kernel.org> (raw)
In-Reply-To: <20240814122633.198562-5-andrei.simion@microchip.com>

On 14/08/2024 14:26, Andrei Simion wrote:
> Rename the usb node according to devicetree
> specification and update the label according
> with the node-specific standard as: ohci, ehci
> or gadget.

Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597

...


> 
> diff --git a/arch/arm/boot/dts/microchip/aks-cdu.dts b/arch/arm/boot/dts/microchip/aks-cdu.dts
> index 742fcf525e1b..52e166c8a365 100644
> --- a/arch/arm/boot/dts/microchip/aks-cdu.dts
> +++ b/arch/arm/boot/dts/microchip/aks-cdu.dts
> @@ -50,13 +50,13 @@ macb0: ethernet@fffc4000 {
>  				status = "okay";
>  			};
>  
> -			usb1: gadget@fffa4000 {
> +			gadget: usb@fffa4000 {
>  				atmel,vbus-gpio = <&pioC 15 GPIO_ACTIVE_HIGH>;
>  				status = "okay";
>  			};
>  		};
>  
> -		usb0: ohci@500000 {
> +		ohci: usb@500000 {

I don't think that these label renames are correct.

>  			num-ports = <2>;
>  			status = "okay";
>  		};
> diff --git a/arch/arm/boot/dts/microchip/animeo_ip.dts b/arch/arm/boot/dts/microchip/animeo_ip.dts
> index 29936bfbeeb7..911c8d9ee013 100644
> --- a/arch/arm/boot/dts/microchip/animeo_ip.dts
> +++ b/arch/arm/boot/dts/microchip/animeo_ip.dts
> @@ -136,7 +136,7 @@ ubi@60000 {
>  			};
>  		};
>  
> -		usb0: ohci@500000 {
> +		ohci: usb@500000 {
>  			num-ports = <2>;
>  			atmel,vbus-gpio = <&pioB 15 GPIO_ACTIVE_LOW>;
>  			status = "okay";
> diff --git a/arch/arm/boot/dts/microchip/at91-ariag25.dts b/arch/arm/boot/dts/microchip/at91-ariag25.dts
> index 713d18f80356..fedcf30a924e 100644
> --- a/arch/arm/boot/dts/microchip/at91-ariag25.dts
> +++ b/arch/arm/boot/dts/microchip/at91-ariag25.dts
> @@ -173,11 +173,11 @@ &usart3 {
>  	status = "okay";
>  };
>  
> -&usb0 {
> +&ohci {
>  	status = "okay";
>  	num-ports = <3>;
>  };
>  
> -&usb1 {
> +&ehci {
>  	status = "okay";
>  };

And how now the sorting works? I don't get the point of it. What is
exactly wrong in the label that justifies the code reshuffling.

BTW, is this some sort of v2? If so, provide changelog and properly
version your patches.

Best regards,
Krzysztof


  reply	other threads:[~2024-08-14 13:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 12:26 [PATCH 0/5] Cosmetic Work for ARM/Microchip (AT91) Andrei Simion
2024-08-14 12:26 ` [PATCH 1/5] ARM: dts: microchip: Clean up spacing and indentation Andrei Simion
2024-08-14 13:20   ` Krzysztof Kozlowski
2024-08-14 13:32     ` Andrei.Simion
2024-08-14 13:57       ` Krzysztof Kozlowski
2024-08-14 14:20         ` Andrei.Simion
2024-08-14 12:26 ` [PATCH 2/5] ARM: dts: microchip: Rename the eeprom nodename Andrei Simion
2024-08-14 12:26 ` [PATCH 3/5] ARM: dts: microchip: Rename the pmic node Andrei Simion
2024-08-14 13:20   ` Krzysztof Kozlowski
2024-08-14 13:58     ` Krzysztof Kozlowski
2024-08-14 12:26 ` [PATCH 4/5] ARM: dts: microchip: Rename the usb node Andrei Simion
2024-08-14 13:22   ` Krzysztof Kozlowski [this message]
2024-09-05 13:51     ` Andrei.Simion
2024-09-05 13:55       ` Krzysztof Kozlowski
2024-08-14 12:26 ` [PATCH 5/5] ARM: dts: microchip: Rename LED sub nodes name Andrei Simion
2024-08-14 13:23   ` Krzysztof Kozlowski
2024-08-15  7:57   ` Alexander Dahl
2024-08-16  8:52     ` Andrei.Simion
2024-08-16  9:06       ` Alexander Dahl
2024-08-20  6:32         ` Andrei.Simion

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=29e5fada-8f8a-4cc0-b1d0-14396f6736a6@kernel.org \
    --to=krzk@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrei.simion@microchip.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=cristian.birsan@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=peda@axentia.se \
    --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).