From: AngeloGioacchino Del Regno <angelogioacchino.delregno@kernel.org>
To: matthias.bgg@gmail.com
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, wenst@chromium.org,
kernel@collabora.com
Subject: Re: [PATCH] arm64: dts: mediatek: mt8195: Add MTU3 nodes and correctly describe USB
Date: Wed, 31 Jan 2024 09:38:49 +0100 [thread overview]
Message-ID: <a331e135-857a-49d2-8644-e8dd0255f372@kernel.org> (raw)
In-Reply-To: <20240115084336.938426-1-angelogioacchino.delregno@collabora.com>
On Mon, 15 Jan 2024 09:43:36 +0100, AngeloGioacchino Del Regno wrote:
> The MT8195 SoC has four USB controllers: only one is a direct path to
> a XHCI controller, while the other three (0, 2 and 3) are behind the
> MTU3 DRD controller instead!
>
> Add the missing MTU3 nodes, default disabled, for controllers 0, 2 and
> 3 and move the related XHCI nodes to be children of their MTU3 DRD to
> correctly describe the SoC.
>
> [...]
Applied, thanks!
[1/1] arm64: dts: mediatek: mt8195: Add MTU3 nodes and correctly describe USB
commit: d464e09e60f024aea0de7adb680a8e8582ab8df8
_______________________________________________
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:[~2024-01-31 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 8:43 [PATCH] arm64: dts: mediatek: mt8195: Add MTU3 nodes and correctly describe USB AngeloGioacchino Del Regno
2024-01-30 11:32 ` AngeloGioacchino Del Regno
2024-01-31 7:14 ` Chen-Yu Tsai
2024-01-31 8:38 ` AngeloGioacchino Del Regno [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=a331e135-857a-49d2-8644-e8dd0255f372@kernel.org \
--to=angelogioacchino.delregno@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=wenst@chromium.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;
as well as URLs for NNTP newsgroup(s).