Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlo Caione" <ccaione@baylibre.com>
To: "Rob Herring (Arm)" <robh@kernel.org>,
	"Carlo Caione" <ccaione@baylibre.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	<devicetree@vger.kernel.org>,
	"Julien Stephan" <jstephan@baylibre.com>,
	<linux-mediatek@lists.infradead.org>,
	"Matthias Brugger" <matthias.bgg@gmail.com>,
	"Conor Dooley" <conor+dt@kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	<linux-arm-kernel@lists.infradead.org>,
	"Chunfeng Yun" <chunfeng.yun@mediatek.com>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>
Subject: Re: [PATCH] dt-bindings: usb: mtu3: Add MT8512
Date: Mon, 24 Aug 2026 09:24:55 +0200	[thread overview]
Message-ID: <DKWZTL9MS4PC.UYFAW9NOZG5N@baylibre.com> (raw)
In-Reply-To: <178576344579.3104650.10771178654777991535.robh@kernel.org>

On Mon Aug 3, 2026 at 3:24 PM CEST, Rob Herring (Arm) wrote:
>
> On Tue, 21 Jul 2026 10:00:28 +0200, Carlo Caione wrote:
>> The MT8512 USB controller uses the standard MTU3 device MAC and IPPC
>> register layout and is handled by the generic mediatek,mtu3 driver. Add
>> the SoC-specific compatible so the controller can be described without a
>> legacy split node.
>> 
>> For now the only user of this is on the U-Boot side but we want to keep
>> bindings in sync.
>> 
>> Signed-off-by: Carlo Caione <ccaione@baylibre.com>
>> ---
>>  Documentation/devicetree/bindings/usb/mediatek,mtu3.yaml | 1 +
>>  1 file changed, 1 insertion(+)
>> 
>
> Acked-by: Rob Herring (Arm) <robh@kernel.org>

Thanks, who should pick up this change?

Cheers,

--
Carlo Caione



      reply	other threads:[~2026-08-24  7:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21  8:00 [PATCH] dt-bindings: usb: mtu3: Add MT8512 Carlo Caione
2026-08-03 13:24 ` Rob Herring (Arm)
2026-08-24  7:24   ` Carlo Caione [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=DKWZTL9MS4PC.UYFAW9NOZG5N@baylibre.com \
    --to=ccaione@baylibre.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chunfeng.yun@mediatek.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jstephan@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=matthias.bgg@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