From: Daniel Palmer <daniel@thingy.jp>
To: Linus Walleij <linusw@kernel.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] Modernize the Faraday FOTG210 driver
Date: Thu, 3 Sep 2026 20:06:26 +0900 [thread overview]
Message-ID: <CAFr9PXnAQJ73Lw3SDfFDC+2LFXks_FSTP3CwWK-vViyZ_==H2Q@mail.gmail.com> (raw)
In-Reply-To: <20260902-gemini-usb-fotg2-v2-0-0057408495d8@kernel.org>
Hi Linus,
On Wed, 2 Sept 2026 at 15:11, Linus Walleij <linusw@kernel.org> wrote:
>
> Replace the private FOTG210 EHCI fork with the common EHCI core and
> quirks for its shifted or missing registers, integrated transaction
> translator, speed reporting, and reset sequence.
Thanks for doing this! I didn't have the time to do this all in one go
so I sent an RFC patch for allowing overrides in the ehci driver as a
prerequisite a few weeks ago.
I will rebase my version of this on top of this series and test on my
hardware when I get some time.
Cheers,
Daniel
next prev parent reply other threads:[~2026-09-03 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 6:11 Linus Walleij
2026-09-02 6:11 ` [PATCH v2 1/5] usb: ehci: support non-standard port status registers Linus Walleij
2026-09-02 14:48 ` Alan Stern
2026-09-02 6:11 ` [PATCH v2 2/5] usb: ehci: add port reset and speed hooks Linus Walleij
2026-09-02 6:11 ` [PATCH v2 3/5] usb: ehci: support additional controller quirks Linus Walleij
2026-09-02 6:11 ` [PATCH v2 4/5] usb: fotg210: use the common EHCI core Linus Walleij
2026-09-02 6:11 ` [PATCH v2 5/5] usb: fotg210-udc: fix endpoint and resource handling Linus Walleij
2026-09-03 11:06 ` Daniel Palmer [this message]
2026-09-03 19:28 ` [PATCH v2 0/5] Modernize the Faraday FOTG210 driver Linus Walleij
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='CAFr9PXnAQJ73Lw3SDfFDC+2LFXks_FSTP3CwWK-vViyZ_==H2Q@mail.gmail.com' \
--to=daniel@thingy.jp \
--cc=gregkh@linuxfoundation.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®