From: Mike Looijmans <mike.looijmans@topic.nl>
To: Conor Dooley <conor@kernel.org>
Cc: linux-usb@vger.kernel.org,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: usb: ti,usb8041: Add binding for TI USB8044 hub controller
Date: Thu, 8 May 2025 17:19:03 +0200 [thread overview]
Message-ID: <583dc73e-23d3-4c8a-a457-f2bf71190e6a@topic.nl> (raw)
In-Reply-To: <20250508-prewashed-jawline-37f53c0f9429@spud>
On 08-05-2025 16:58, Conor Dooley wrote:
> On Wed, May 07, 2025 at 03:11:43PM +0200, Mike Looijmans wrote:
>> The TI USB8044 is similar to the USB8041.
> Similar how? Why's a fallback not suitable?
I don't quite understand what is meant by "fallback" here?
It's similar in that the USB8044 provides the same functionality and can
use the same driver as the USB8041, all that is needed is to add the
PID/VID values.
M.
>
>> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
>> ---
>>
>> Documentation/devicetree/bindings/usb/ti,usb8041.yaml | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/usb/ti,usb8041.yaml b/Documentation/devicetree/bindings/usb/ti,usb8041.yaml
>> index c2e29bd61e11..fd6b35a40a5b 100644
>> --- a/Documentation/devicetree/bindings/usb/ti,usb8041.yaml
>> +++ b/Documentation/devicetree/bindings/usb/ti,usb8041.yaml
>> @@ -4,7 +4,7 @@
>> $id: http://devicetree.org/schemas/usb/ti,usb8041.yaml#
>> $schema: http://devicetree.org/meta-schemas/core.yaml#
>>
>> -title: TI USB8041 USB 3.0 hub controller
>> +title: TI USB8041 and USB8044 USB 3.0 hub controllers
>>
>> maintainers:
>> - Alexander Stein <alexander.stein@ew.tq-group.com>
>> @@ -17,6 +17,8 @@ properties:
>> enum:
>> - usb451,8140
>> - usb451,8142
>> + - usb451,8440
>> + - usb451,8442
>>
>> reg: true
>>
>> --
>> 2.34.1
>>
>>
>> Met vriendelijke groet / kind regards,
>>
>> Mike Looijmans
>> System Expert
>>
>>
>> TOPIC Embedded Products B.V.
>> Materiaalweg 4, 5681 RJ Best
>> The Netherlands
>>
>> T: +31 (0) 499 33 69 69
>> E: mike.looijmans@topic.nl
>> W: www.topic.nl
>>
>> Please consider the environment before printing this e-mail
--
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijmans@topic.nl
W: www.topic.nl
next prev parent reply other threads:[~2025-05-08 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.3e03400f-766d-4690-8f43-cbea2cac93d8@emailsignatures365.codetwo.com>
[not found] ` <20250507131143.2243079-1-mike.looijmans@topic.nl>
2025-05-07 13:11 ` [PATCH 2/2] dt-bindings: usb: ti,usb8041: Add binding for TI USB8044 hub controller Mike Looijmans
2025-05-08 14:58 ` Conor Dooley
2025-05-08 15:19 ` Mike Looijmans [this message]
2025-05-08 15:53 ` Conor Dooley
2025-05-09 5:56 ` Mike Looijmans
2025-05-09 15:48 ` Conor Dooley
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=583dc73e-23d3-4c8a-a457-f2bf71190e6a@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@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