From: sashiko-bot@kernel.org
To: "Roman Vivchar" <rva333@protonmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v3 2/3] usb: mtu3: add SoC platform data for FIFO quirk handling
Date: Sat, 07 Nov 2026 15:03:06 +0000 [thread overview]
Message-ID: <sashiko-outbox-202980@kernel.org> (raw)
In-Reply-To: <20261107-6595-mtu3-v3-2-f36bc569cb47@protonmail.com>
> From: Roman Vivchar <rva333@protonmail.com>
>
> Some SoCs, such as mt6595, require specific quirks for the MTU3 to
> function properly.
>
> The mt6595 IP block doesn't support multiple slots for the FIFO,
> resulting FIFO wrap.
>
> Fix this by adding platform data with a field to handle FIFO limitation.
> No functional changes for existing SoCs.
>
> Assisted-by: LLM (debugging)
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Signed-off-by: Roman Vivchar <rva333@protonmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261107-6595-mtu3-v3-0-f36bc569cb47@protonmail.com?part=2
next prev parent reply other threads:[~2026-11-07 15:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 14:54 [PATCH v3 0/3] usb: mtu3: add mt6595 support Roman Vivchar
2026-11-07 14:54 ` Roman Vivchar via B4 Relay
2026-11-07 14:54 ` [PATCH v3 1/3] dt-bindings: usb: mtu3: add mt6595 Roman Vivchar
2026-11-07 14:54 ` Roman Vivchar via B4 Relay
2026-11-07 15:00 ` sashiko-bot
2026-11-07 14:54 ` [PATCH v3 2/3] usb: mtu3: add SoC platform data for FIFO quirk handling Roman Vivchar
2026-11-07 14:54 ` Roman Vivchar via B4 Relay
2026-11-07 15:03 ` sashiko-bot [this message]
2026-11-07 14:54 ` [PATCH v3 3/3] usb: mtu3: add mt6595 support Roman Vivchar
2026-11-07 14:54 ` Roman Vivchar via B4 Relay
2026-11-07 14:58 ` sashiko-bot
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=sashiko-outbox-202980@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rva333@protonmail.com \
--cc=sashiko-reviews@lists.linux.dev \
/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.