From: Roman Vivchar via B4 Relay <devnull+rva333.protonmail.com@kernel.org>
To: Chunfeng Yun <chunfeng.yun@mediatek.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Roman Vivchar <rva333@protonmail.com>
Subject: [PATCH v2 0/3] usb: mtu3: add mt6595 support
Date: Tue, 22 Sep 2026 13:36:39 +0300 [thread overview]
Message-ID: <20260922-6595-mtu3-v2-0-71203a362b36@protonmail.com> (raw)
This patch series adds mt6595 SoC support to the mtu3 driver.
Unlike the mt8173 and newer controllers, the 6595 uses older IP revision
that can handle only one FIFO slot. Without this series, the current
driver implementation results in 2 to 4 lost bytes on USB transfers.
In mediatek sources, mt6595 is sometimes called 6795. Most of their
clocks/pins are also compatible. It's not clear if 6795 has the same
issue or simply lacks T-PHY patch. Other (rare) mobile SoCs with mtu3,
like mt6757 or 6771, don't need this series.
Another thing worth mentioning, this series is not enough for the USB on
6595. The other T-PHY patch is required to get the link up. This issue
has been observed on some 65xx and most 67xx SoCs. Though this is a
subject for the separate discussion.
Signed-off-by: Roman Vivchar <rva333@protonmail.com>
---
Changes in v2:
- Reword patch 2 commit title
- single_slot -> fifo_single_slot naming
- Drop redundant platform data check
- Link to v1: https://patch.msgid.link/20260917-6595-mtu3-v1-0-a2ba7c230d68@protonmail.com
---
Roman Vivchar (3):
dt-bindings: usb: mtu3: add mt6595
usb: mtu3: add SoC platform data for FIFO quirk handling
usb: mtu3: add mt6595 support
Documentation/devicetree/bindings/usb/mediatek,mtu3.yaml | 1 +
drivers/usb/mtu3/mtu3.h | 9 +++++++++
drivers/usb/mtu3/mtu3_core.c | 3 +++
drivers/usb/mtu3/mtu3_gadget.c | 8 ++++++--
drivers/usb/mtu3/mtu3_plat.c | 13 +++++++++++--
5 files changed, 30 insertions(+), 4 deletions(-)
---
base-commit: 8d3ae59288f1e7d58d76558a6ee96d533bc5019f
change-id: 20260914-6595-mtu3-82b3048e41ea
Best regards,
--
Roman Vivchar <rva333@protonmail.com>
next reply other threads:[~2026-09-22 10:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 10:36 Roman Vivchar via B4 Relay [this message]
2026-09-22 10:36 ` [PATCH v2 1/3] dt-bindings: usb: mtu3: add mt6595 Roman Vivchar via B4 Relay
2026-09-28 7:51 ` Krzysztof Kozlowski
2026-09-22 10:36 ` [PATCH v2 2/3] usb: mtu3: add SoC platform data for FIFO quirk handling Roman Vivchar via B4 Relay
2026-09-22 11:46 ` AngeloGioacchino Del Regno
2026-09-22 10:36 ` [PATCH v2 3/3] usb: mtu3: add mt6595 support Roman Vivchar via B4 Relay
2026-09-22 11:46 ` AngeloGioacchino Del Regno
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=20260922-6595-mtu3-v2-0-71203a362b36@protonmail.com \
--to=devnull+rva333.protonmail.com@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunfeng.yun@mediatek.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-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=rva333@protonmail.com \
/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