From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Roy Luo" <royluo@google.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Peter Griffin" <peter.griffin@linaro.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Thinh Nguyen" <Thinh.Nguyen@synopsys.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>
Cc: Badhri Jagan Sridharan <badhri@google.com>,
Doug Anderson <dianders@google.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
Joy Chakraborty <joychakr@google.com>,
Naveen Kumar <mnkumar@google.com>
Subject: Re: [PATCH v9 1/2] dt-bindings: usb: dwc3: Add Google Tensor G5 DWC3
Date: Fri, 5 Dec 2025 18:14:12 +0100 [thread overview]
Message-ID: <3b367841-326c-4697-9fe9-041a32001d94@kernel.org> (raw)
In-Reply-To: <20251205-controller-v9-1-9f158b18f979@google.com>
On 05/12/2025 03:26, Roy Luo wrote:
> Document the device tree bindings for the DWC3 USB controller found in
> Google Tensor SoCs, starting with the G5 generation (codename: laguna).
>
> The Tensor G5 silicon represents a complete architectural departure from
> previous generations (like gs101), including entirely new clock/reset
> schemes, top-level wrapper and register interface. Consequently,
> existing Samsung/Exynos DWC3 USB bindings are incompatible, necessitating
> this new device tree binding.
>
> The USB controller on Tensor G5 is based on Synopsys DWC3 IP and features
> Dual-Role Device single port with hibernation support.
>
> Signed-off-by: Roy Luo <royluo@google.com>
> ---
> .../devicetree/bindings/usb/google,lga-dwc3.yaml | 140 +++++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 141 insertions(+)
>
Nothing explains reason to ignore review. I am not doing same work
twice, please respect maintainers' time.
<form letter>
This is a friendly reminder during the review process.
It looks like you received a tag and forgot to add it.
If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions
of patchset, under or above your Signed-off-by tag, unless patch changed
significantly (e.g. new properties added to the DT bindings). Tag is
"received", when provided in a message replied to you on the mailing
list. Tools like b4 can help here. However, there's no need to repost
patches *only* to add the tags. The upstream maintainer will do that for
tags received on the version they apply.
Please read:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577
If a tag was not added on purpose, please state why and what changed.
</form letter>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-05 17:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 2:26 [PATCH v9 0/2] Add Google Tensor SoC USB controller support Roy Luo
2025-12-05 2:26 ` [PATCH v9 1/2] dt-bindings: usb: dwc3: Add Google Tensor G5 DWC3 Roy Luo
2025-12-05 17:14 ` Krzysztof Kozlowski [this message]
2025-12-06 10:47 ` Krzysztof Kozlowski
2025-12-05 2:26 ` [PATCH v9 2/2] usb: dwc3: Add Google Tensor SoC DWC3 glue driver Roy Luo
2025-12-05 6:05 ` Greg Kroah-Hartman
2025-12-05 7:14 ` Roy Luo
2025-12-16 23:34 ` Thinh Nguyen
2025-12-17 0:25 ` Roy Luo
2025-12-17 13:24 ` Greg Kroah-Hartman
2025-12-17 19:17 ` Roy Luo
2025-12-17 20:14 ` Doug Anderson
2025-12-18 1:34 ` Roy Luo
2025-12-18 6:27 ` Greg Kroah-Hartman
2025-12-18 7:06 ` Krzysztof Kozlowski
2025-12-18 19:02 ` Roy Luo
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=3b367841-326c-4697-9fe9-041a32001d94@kernel.org \
--to=krzk@kernel.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=andre.draszik@linaro.org \
--cc=badhri@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=joychakr@google.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mnkumar@google.com \
--cc=p.zabel@pengutronix.de \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=royluo@google.com \
--cc=tudor.ambarus@linaro.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 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.