U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eugen Hristev <eugen.hristev@linaro.org>
To: Mattijs Korpershoek <mkorpershoek@kernel.org>,
	Zixun LI <admin@hifiphile.com>, Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH v2 2/3] ARM: dts: sam9x60: Add USB gadget DT node.
Date: Tue, 1 Apr 2025 13:40:42 +0300	[thread overview]
Message-ID: <ff98b27c-07d8-4f49-9696-fd09ab2ab499@linaro.org> (raw)
In-Reply-To: <87v7ronqdw.fsf@baylibre.com>



On 4/1/25 13:10, Mattijs Korpershoek wrote:
> Hi Zixun,
> 
> Thank you for the patch.
> 
> On lun., mars 31, 2025 at 18:26, Zixun LI <admin@hifiphile.com> wrote:
> 
>> Add the USB gadget DT node for the sam9x60 SoC's.
>>
>> Signed-off-by: Zixun LI <admin@hifiphile.com>
> 
> Nitpick: title (subject) should not finish with a period (.)
> 
> This can be fixed up by the maintainer that will apply the patches.
> 
> Eugen, This is assigned to me on patchwork:
> https://patchwork.ozlabs.org/project/uboot/list/?series=450655
> 
> Can I pick up all 3 patches or do you prefer to pick up [2/3] and [3/3] ?

It is better that I take these two, because there are some pending
changes on the same DT for the next merge window, so it would avoid
conflicts.
Reassign them to me in patchwork please.

> 
> Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>
> 
>> ---
>>  arch/arm/dts/sam9x60.dtsi | 13 +++++++++++++
>>  1 file changed, 13 insertions(+)
>>
>> diff --git a/arch/arm/dts/sam9x60.dtsi b/arch/arm/dts/sam9x60.dtsi
>> index 3b684fc63d5..ea2647e5fc9 100644
>> --- a/arch/arm/dts/sam9x60.dtsi
>> +++ b/arch/arm/dts/sam9x60.dtsi
>> @@ -69,6 +69,19 @@
>>  		#size-cells = <1>;
>>  		ranges;
>>  
>> +		usb0: gadget@500000 {
>> +			#address-cells = <1>;
>> +			#size-cells = <0>;
>> +			compatible = "microchip,sam9x60-udc";
>> +			reg = <0x500000 0x100000>,
>> +				<0xf803c000 0x400>;
>> +			clocks = <&pmc PMC_TYPE_PERIPHERAL 23>, <&pmc PMC_TYPE_CORE 8>;
>> +			clock-names = "pclk", "hclk";
>> +			assigned-clocks = <&pmc PMC_TYPE_CORE 8>;
>> +			assigned-clock-rates = <480000000>;
>> +			status = "disabled";
>> +		};
>> +
>>  		usb1: usb@600000 {
>>  			compatible = "atmel,at91rm9200-ohci", "usb-ohci";
>>  			reg = <0x00600000 0x100000>;
>> -- 
>> 2.49.0


  reply	other threads:[~2025-04-01 10:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250331162611.1557759-1-admin@hifiphile.com>
2025-03-31 16:26 ` [PATCH v2 1/3] usb: gadget: atmel: Add SAM9X60 support Zixun LI
2025-04-01 10:07   ` Mattijs Korpershoek
2025-04-10  8:49   ` (subset) " Mattijs Korpershoek
2025-04-18 10:43     ` Eugen Hristev
2025-03-31 16:26 ` [PATCH v2 2/3] ARM: dts: sam9x60: Add USB gadget DT node Zixun LI
2025-03-31 20:34   ` Eugen Hristev
2025-04-01 10:10   ` Mattijs Korpershoek
2025-04-01 10:40     ` Eugen Hristev [this message]
2025-04-01 12:27       ` Mattijs Korpershoek
2025-03-31 16:26 ` [PATCH v2 3/3] ARM: dts: at91: sam9x60-curiosity: Enable USB gadget node Zixun LI
2025-03-31 20:34   ` Eugen Hristev
2025-04-01 10:11   ` Mattijs Korpershoek

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=ff98b27c-07d8-4f49-9696-fd09ab2ab499@linaro.org \
    --to=eugen.hristev@linaro.org \
    --cc=admin@hifiphile.com \
    --cc=mkorpershoek@kernel.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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