From: Michael Zaidman <michael.zaidman@gmail.com>
To: Aaron Jones <aaron.jones@ftdichip.com>
Cc: jikos@kernel.org, benjamin.tissoires@redhat.com, wsa@kernel.org,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
linux-i2c@vger.kernel.org
Subject: Re: [PATCHv2 1/1] HID: ft260: add usb hid to i2c host bridge driver
Date: Thu, 4 Mar 2021 14:46:33 +0200 [thread overview]
Message-ID: <20210304124633.GA23038@michael-VirtualBox> (raw)
In-Reply-To: <20210304111406.3482-1-aaron.jones@ftdichip.com>
On Thu, Mar 04, 2021 at 11:14:06AM +0000, Aaron Jones wrote:
> From: Aaron Jones(FTDI-UK) <aaron.jones@ftdichip.com>
>
> On Fri, Feb 19, 2021 at 06:36:44PM +0200, Michael Zaidman wrote:
> > The FTDI FT260 chip implements USB to I2C/UART bridges through two
> > USB HID class interfaces. The first - for I2C, and the second for UART.
> > Each interface is independent, and the kernel detects it as a separate
> > USB hidraw device.
> >
> > This commit adds I2C host adapter support.
> >
> > Signed-off-by:Michael Zaidman <michael.zaidman@gmail.com>
>
> I've applied the patch, ran some tests with a UMFT260EV1A evaluation board,
> and found no issues with the functionality it provides.
>
> Tested-by: Aaron Jones (FTDI-UK) <aaron.jones@ftdichip.com>
Aaron, thanks for giving it a try - much appreciated!
I will add your "Tested-by:" to the next version of the patch
once I receive any feedback.
next prev parent reply other threads:[~2021-03-04 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 16:36 [PATCH v2 0/1] HID: ft260: add usb hid to i2c host bridge driver Michael Zaidman
2021-02-19 16:36 ` [PATCH v2 1/1] " Michael Zaidman
2021-03-04 11:14 ` [PATCHv2 " Aaron Jones
2021-03-04 12:46 ` Michael Zaidman [this message]
2021-03-16 7:25 ` Jiri Kosina
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=20210304124633.GA23038@michael-VirtualBox \
--to=michael.zaidman@gmail.com \
--cc=aaron.jones@ftdichip.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@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;
as well as URLs for NNTP newsgroup(s).