From: Herve Codina <herve.codina@bootlin.com>
To: <Claudiu.Beznea@microchip.com>
Cc: devicetree@vger.kernel.org, alexandre.belloni@bootlin.com,
thomas.petazzoni@bootlin.com, sboyd@kernel.org,
gregkh@linuxfoundation.org, mturquette@baylibre.com,
linux-usb@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, Horatiu.Vultur@microchip.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 3/3] ARM: dts: lan966x: Add UDPHS support
Date: Fri, 1 Jul 2022 09:09:09 +0200 [thread overview]
Message-ID: <20220701090909.50654cb4@bootlin.com> (raw)
In-Reply-To: <f4f14941-6839-5691-b2d1-adb049118a4d@microchip.com>
Hi Claudiu,
On Thu, 30 Jun 2022 09:31:00 +0000
<Claudiu.Beznea@microchip.com> wrote:
> On 25.05.2022 10:10, Herve Codina wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > Add UDPHS (the USB High Speed Device Port controller) support.
> >
> > The both lan966x SOCs (LAN9662 and LAN9668) have the same UDPHS
> > IP. This IP is also 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..e086df741f99 100644
> > --- a/arch/arm/boot/dts/lan966x.dtsi
> > +++ b/arch/arm/boot/dts/lan966x.dtsi
> > @@ -196,6 +196,17 @@ watchdog: watchdog@e0090000 {
> > status = "disabled";
> > };
> >
> > + udc: usb@e0808000 {
> > + compatible = "microchip,lan9662-udc",
> > + "atmel,sama5d3-udc";
> > + reg = <0x00200000 0x80000>,
> > + <0xe0808000 0x400>;
> > + interrupts = <GIC_SPI 76 IRQ_TYPE_LEVEL_HIGH>;
> > + clocks = <&clks GCK_GATE_UDPHS>, <&nic_clk>;
> > + clock-names = "pclk", "hclk";
> > + status = "disabled";
> > + };
> > +
>
> This doesn't apply clean on top of v5.19-rc1. Can you check and resend?
Sure,
I am going to send a rebased version of this series.
Thanks,
Hervé
--
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
prev parent reply other threads:[~2022-07-01 7:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 7:10 [PATCH v3 0/3] Microchip LAN966x USB device support Herve Codina
2022-05-25 7:10 ` [PATCH v3 1/3] clk: lan966x: Fix the lan966x clock gate register address Herve Codina
2022-05-25 7:10 ` [PATCH v3 2/3] dt-bindings: usb: atmel: Add Microchip LAN9662 compatible string Herve Codina
2022-05-25 7:10 ` [PATCH v3 3/3] ARM: dts: lan966x: Add UDPHS support Herve Codina
2022-06-30 9:31 ` Claudiu.Beznea
2022-07-01 7:09 ` Herve Codina [this message]
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=20220701090909.50654cb4@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@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=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 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).