From: Krzysztof Kozlowski <krzk@kernel.org>
To: Marek Vasut <marex@nabladev.com>
Cc: linux-arm-kernel@lists.infradead.org,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-usb@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: usb: generic-ohci: Document ST STM32MP1 SoC compatibles
Date: Mon, 31 Aug 2026 11:00:44 +0200 [thread overview]
Message-ID: <756463ff-f2ef-4aa5-add1-73490686475d@kernel.org> (raw)
In-Reply-To: <20260831-gay-colorful-cat-edf6c7@quoll>
On 31/08/2026 10:51, Krzysztof Kozlowski wrote:
> On Fri, Aug 28, 2026 at 05:01:26PM +0200, Marek Vasut wrote:
>> Document SoC compatibles for ST STM32MP13xx and STM32MP15xx series of
>> SoC, so they can be used as more accurate compatible in SoC DTSI. The
>> SoC DTSI currently use plain "generic-ohci" which is not future proof.
>>
>> Signed-off-by: Marek Vasut <marex@nabladev.com>
>> ---
>
> This should go also with your access controllers property. What
> happened to it?
>
Ah, I mixed patchsets/devices.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
prev parent reply other threads:[~2026-08-31 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 15:01 [PATCH 1/3] dt-bindings: usb: generic-ohci: Document ST STM32MP1 SoC compatibles Marek Vasut
2026-08-28 15:01 ` [PATCH 2/3] ARM: dts: stm32: Use STM32MP13xx compatible string for OHCI USB controller Marek Vasut
2026-08-28 15:01 ` [PATCH 3/3] ARM: dts: stm32: Use STM32MP15xx " Marek Vasut
2026-08-28 15:09 ` [PATCH 1/3] dt-bindings: usb: generic-ohci: Document ST STM32MP1 SoC compatibles sashiko-bot
2026-08-31 8:51 ` Krzysztof Kozlowski
2026-08-31 9:00 ` Krzysztof Kozlowski [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=756463ff-f2ef-4aa5-add1-73490686475d@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-usb@vger.kernel.org \
--cc=marex@nabladev.com \
--cc=mcoquelin.stm32@gmail.com \
--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