From: Herve Codina <herve.codina@bootlin.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH 3/3] ARM: dts: lan966x: Add UDPHS support
Date: Fri, 20 May 2022 14:37:26 +0200 [thread overview]
Message-ID: <20220520143726.6dd324fb@bootlin.com> (raw)
In-Reply-To: <2945e445-3453-a45f-7d3d-3b07bf350b47@linaro.org>
Hi Krzysztof, Sergei
On Fri, 13 May 2022 14:54:26 +0200
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> On 13/05/2022 12:58, Herve Codina wrote:
> > Add UDPHS (the USB High Speed Device Port controller) support.
> > The UDPHS IP present in the lan966x SOC is the same as the one
> > present in the SAMA5D3 SOC
> >
> > Signed-off-by: Herve Codina <herve.codina@bootlin.com>
> > ---
> > arch/arm/boot/dts/lan966x.dtsi | 11 +++++++++++
> > 1 file changed, 11 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/lan966x.dtsi b/arch/arm/boot/dts/lan966x.dtsi
> > index 7d2869648050..4c09f3166d27 100644
> > --- a/arch/arm/boot/dts/lan966x.dtsi
> > +++ b/arch/arm/boot/dts/lan966x.dtsi
> > @@ -211,6 +211,17 @@ can0: can@e081c000 {
> > status = "disabled";
> > };
> >
> > + udc: udphs@e0808000 {
>
> Generic node names, so it looks like usb. For example HCD schema
> requires it. I am not sure which bindings are used here, but anyway once
> they might require usb...
>
HCD are related to the Host controller.
Here we are talking about a device.
In existing bindings related to USB device (or OTG as an OTG can be a
host or a device) on several SOCs, we can find:
- usb1: gadget@fffa4000
- usb_otg: usb@1c13000
- usb: usb@47400000
- udc: usb@13040000
- usb_otg_hs: usb_otg_hs@4a0ab000
So I will change to
udc: usb@e0808000
Is that ok for you ?
Regards,
Herve
--
Hervé Codina, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
WARNING: multiple messages have this Message-ID (diff)
From: Herve Codina <herve.codina@bootlin.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: devicetree@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Stephen Boyd <sboyd@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-usb@vger.kernel.org, linux-clk@vger.kernel.org,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] ARM: dts: lan966x: Add UDPHS support
Date: Fri, 20 May 2022 14:37:26 +0200 [thread overview]
Message-ID: <20220520143726.6dd324fb@bootlin.com> (raw)
In-Reply-To: <2945e445-3453-a45f-7d3d-3b07bf350b47@linaro.org>
Hi Krzysztof, Sergei
On Fri, 13 May 2022 14:54:26 +0200
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> On 13/05/2022 12:58, Herve Codina wrote:
> > Add UDPHS (the USB High Speed Device Port controller) support.
> > The UDPHS IP present in the lan966x SOC is the same as the one
> > present in the SAMA5D3 SOC
> >
> > Signed-off-by: Herve Codina <herve.codina@bootlin.com>
> > ---
> > arch/arm/boot/dts/lan966x.dtsi | 11 +++++++++++
> > 1 file changed, 11 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/lan966x.dtsi b/arch/arm/boot/dts/lan966x.dtsi
> > index 7d2869648050..4c09f3166d27 100644
> > --- a/arch/arm/boot/dts/lan966x.dtsi
> > +++ b/arch/arm/boot/dts/lan966x.dtsi
> > @@ -211,6 +211,17 @@ can0: can@e081c000 {
> > status = "disabled";
> > };
> >
> > + udc: udphs@e0808000 {
>
> Generic node names, so it looks like usb. For example HCD schema
> requires it. I am not sure which bindings are used here, but anyway once
> they might require usb...
>
HCD are related to the Host controller.
Here we are talking about a device.
In existing bindings related to USB device (or OTG as an OTG can be a
host or a device) on several SOCs, we can find:
- usb1: gadget@fffa4000
- usb_otg: usb@1c13000
- usb: usb@47400000
- udc: usb@13040000
- usb_otg_hs: usb_otg_hs@4a0ab000
So I will change to
udc: usb@e0808000
Is that ok for you ?
Regards,
Herve
--
Hervé Codina, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-20 12:37 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 10:58 [PATCH 0/3] Microchip LAN966x USB device support Herve Codina
2022-05-13 10:58 ` Herve Codina
2022-05-13 10:58 ` [PATCH 1/3] clk: lan966x: Fix the lan966x clock gate register address Herve Codina
2022-05-13 10:58 ` Herve Codina
2022-05-13 10:58 ` [PATCH 2/3] dt-bindings: usb: atmel: Add Microchip LAN966x compatible string Herve Codina
2022-05-13 10:58 ` Herve Codina
2022-05-13 12:57 ` Krzysztof Kozlowski
2022-05-13 12:57 ` Krzysztof Kozlowski
2022-05-20 11:34 ` Herve Codina
2022-05-20 11:34 ` Herve Codina
2022-05-20 11:40 ` Krzysztof Kozlowski
2022-05-20 11:40 ` Krzysztof Kozlowski
2022-05-20 12:21 ` Herve Codina
2022-05-20 12:21 ` Herve Codina
2022-05-20 12:50 ` Krzysztof Kozlowski
2022-05-20 12:50 ` Krzysztof Kozlowski
2022-05-20 13:02 ` Herve Codina
2022-05-20 13:02 ` Herve Codina
2022-05-20 13:38 ` Krzysztof Kozlowski
2022-05-20 13:38 ` Krzysztof Kozlowski
2022-05-20 13:52 ` Alexandre Belloni
2022-05-20 13:52 ` Alexandre Belloni
2022-05-20 14:05 ` Krzysztof Kozlowski
2022-05-20 14:05 ` Krzysztof Kozlowski
2022-05-20 14:12 ` Herve Codina
2022-05-20 14:12 ` Herve Codina
2022-05-13 10:58 ` [PATCH 3/3] ARM: dts: lan966x: Add UDPHS support Herve Codina
2022-05-13 10:58 ` Herve Codina
2022-05-13 12:54 ` Krzysztof Kozlowski
2022-05-13 12:54 ` Krzysztof Kozlowski
2022-05-20 12:37 ` Herve Codina [this message]
2022-05-20 12:37 ` Herve Codina
2022-05-20 12:48 ` Krzysztof Kozlowski
2022-05-20 12:48 ` Krzysztof Kozlowski
2022-05-14 9:35 ` Sergei Shtylyov
2022-05-14 9:35 ` Sergei Shtylyov
-- strict thread matches above, loose matches on Subject: below --
2022-05-20 15:23 [PATCH 0/3] Microchip LAN966x USB device support Herve Codina
2022-05-20 15:23 ` [PATCH 3/3] ARM: dts: lan966x: Add UDPHS support Herve Codina
2022-05-20 15:23 ` Herve Codina
2022-05-23 8:10 ` Claudiu.Beznea
2022-05-23 8:10 ` Claudiu.Beznea
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=20220520143726.6dd324fb@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=horatiu.vultur@microchip.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.