From: <Claudiu.Beznea@microchip.com>
To: <herve.codina@bootlin.com>, <gregkh@linuxfoundation.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<mturquette@baylibre.com>, <sboyd@kernel.org>,
<Horatiu.Vultur@microchip.com>
Cc: <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@bootlin.com>, <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v5 2/3] dt-bindings: usb: atmel: Add Microchip LAN9662 compatible string
Date: Tue, 5 Jul 2022 07:48:01 +0000 [thread overview]
Message-ID: <a4bac810-e714-afec-8bbc-65ee7502c7f8@microchip.com> (raw)
In-Reply-To: <20220704102845.168438-3-herve.codina@bootlin.com>
On 04.07.2022 13:28, Herve Codina wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> The USB device controller available in the Microchip LAN9662 SOC
> is the same IP as the one present in the SAMA5D3 SOC.
>
> Add the LAN9662 compatible string and set the SAMA5D3 compatible
> string as a fallback for the LAN9662.
>
> Signed-off-by: Herve Codina <herve.codina@bootlin.com>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Applied to at91-dt, thanks!
> ---
> Documentation/devicetree/bindings/usb/atmel-usb.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/usb/atmel-usb.txt b/Documentation/devicetree/bindings/usb/atmel-usb.txt
> index f512f0290728..12183ef47ee4 100644
> --- a/Documentation/devicetree/bindings/usb/atmel-usb.txt
> +++ b/Documentation/devicetree/bindings/usb/atmel-usb.txt
> @@ -87,6 +87,9 @@ Required properties:
> "atmel,at91sam9g45-udc"
> "atmel,sama5d3-udc"
> "microchip,sam9x60-udc"
> + "microchip,lan9662-udc"
> + For "microchip,lan9662-udc" the fallback "atmel,sama5d3-udc"
> + is required.
> - reg: Address and length of the register set for the device
> - interrupts: Should contain usba interrupt
> - clocks: Should reference the peripheral and host clocks
> --
> 2.35.3
>
next prev parent reply other threads:[~2022-07-05 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 10:28 [PATCH v5 0/3] Microchip LAN966x USB device support Herve Codina
2022-07-04 10:28 ` [PATCH v5 1/3] clk: lan966x: Fix the lan966x clock gate register address Herve Codina
2022-07-05 8:51 ` Claudiu.Beznea
2022-07-05 13:00 ` Michael Walle
2022-07-19 7:04 ` Stephen Boyd
2022-07-04 10:28 ` [PATCH v5 2/3] dt-bindings: usb: atmel: Add Microchip LAN9662 compatible string Herve Codina
2022-07-05 7:48 ` Claudiu.Beznea [this message]
2022-07-04 10:28 ` [PATCH v5 3/3] ARM: dts: lan966x: Add UDPHS support Herve Codina
2022-07-05 7:48 ` 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=a4bac810-e714-afec-8bbc-65ee7502c7f8@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=herve.codina@bootlin.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=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