From: Francesco Lavra <flavra@baylibre.com>
To: Andi Shyti <andi.shyti@kernel.org>,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH v4] i2c: Add FTDI FT4222H USB I2C adapter
Date: Thu, 10 Sep 2026 11:16:35 +0200 [thread overview]
Message-ID: <71023ac4c8f2eab6dc5f7dc135fd22d2f07a5d5f.camel@baylibre.com> (raw)
In-Reply-To: <7d9d7bfac46269c1a66b6aff25a28d12354cc3c3.camel@baylibre.com>
On Mon, 2026-07-27 at 10:07 +0200, Francesco Lavra wrote:
> Another friendly ping
>
> On Thu, 2026-04-30 at 17:40 +0200, Francesco Lavra wrote:
> > Friendly ping
> >
> > On Wed, 2026-02-25 at 12:20 +0100, Francesco Lavra wrote:
> > > FT4222H exports a USB interface to operate as I2C bus master when set
> > > up
> > > (via the DCNF pins) in configuration mode 0 or 3.
> > > The USB communication protocol implemented by the FT4222 chip is not
> > > publicly documented, therefore the name assigned to the various
> > > defines
> > > used in the USB communication code is a semi-educated guess after
> > > sniffing
> > > USB traffic generated with the FTDI FT4222 userspace library.
> > >
> > > Signed-off-by: Francesco Lavra <flavra@baylibre.com>
It has been more than six months since I sent v4 of this patch, and there
has not been any followup on this, other than my attempts to revive this
thread. And that is after all review comments from the previous iterations
have been addressed.
Is there anything else I should do to help this patch move forward?
Thanks
prev parent reply other threads:[~2026-09-10 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 11:20 Francesco Lavra
2026-04-30 15:40 ` Francesco Lavra
2026-07-27 8:07 ` Francesco Lavra
2026-09-10 9:16 ` Francesco Lavra [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=71023ac4c8f2eab6dc5f7dc135fd22d2f07a5d5f.camel@baylibre.com \
--to=flavra@baylibre.com \
--cc=andi.shyti@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®