devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Andrei.Simion@microchip.com>
To: <krzk@kernel.org>, <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: Thu, 5 Sep 2024 13:51:19 +0000	[thread overview]
Message-ID: <035ef8b9-36d5-4696-b576-35e051b687d5@microchip.com> (raw)
In-Reply-To: <29e5fada-8f8a-4cc0-b1d0-14396f6736a6@kernel.org>

Hi,

On 14.08.2024 16:22, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> 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
> 
> ...
> 

In V2 I will wrap the commit message according to Linux coding style / submission process

> 
>>
>> 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.
> 

I checked in other dts dtsi (other silicon vendors) the USB node 
and it uses ohci, ehci, gadget, etc as a label.  Also, I verified the
address in the datasheet and they are correctly labeled (meant that 
they were: usb gadget, usb ohci, usb ehci)

From what point of view is it not correct?
I would like to know so I can do it right


>>                       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.
> 

The point is to be easy to determine what kind of standard 
represents/implements the usb node.

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

It was a new series and from now on there will be v2

BR,
Andrei Simion

> Best regards,
> Krzysztof
> 


  reply	other threads:[~2024-09-05 13:51 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
2024-09-05 13:51     ` Andrei.Simion [this message]
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=035ef8b9-36d5-4696-b576-35e051b687d5@microchip.com \
    --to=andrei.simion@microchip.com \
    --cc=Cristian.Birsan@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).