From: Greg KH <gregkh@linuxfoundation.org>
To: Mary Strodl <mstrodl@csh.rit.edu>
Cc: linux-kernel@vger.kernel.org, linus.walleij@linaro.org,
brgl@bgdev.pl, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v5] gpio: add support for FTDI's MPSSE as GPIO
Date: Sun, 13 Oct 2024 16:52:28 +0200 [thread overview]
Message-ID: <2024101314-rephrase-lark-c93a@gregkh> (raw)
In-Reply-To: <20241009131131.1618329-1-mstrodl@csh.rit.edu>
On Wed, Oct 09, 2024 at 09:11:31AM -0400, Mary Strodl wrote:
> FTDI FT2232H is a USB to GPIO chip. Sealevel produces some devices
> with this chip. FT2232H presents itself as a composite device with two
> interfaces (each is an "MPSSE"). Each MPSSE has two banks (high and low)
> of 8 GPIO each. I believe some MPSSE's have only one bank, but I don't
> know how to identify them (I don't have any for testing) and as a result
> are unsupported for the time being.
>
> Additionally, this driver provides software polling-based interrupts for
> edge detection. For the Sealevel device I have to test with, this works
> well because there is hardware debouncing. From talking to Sealevel's
> people, this is their preferred way to do edge detection.
>
> Signed-off-by: Mary Strodl <mstrodl@csh.rit.edu>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> ---
>
> (Resent because I forgot to cc gregkh last time)
USB stuff looks sane, no objection from me there.
next prev parent reply other threads:[~2024-10-13 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 13:11 [PATCH v5] gpio: add support for FTDI's MPSSE as GPIO Mary Strodl
2024-10-13 14:52 ` Greg KH [this message]
2024-10-14 7:08 ` Bartosz Golaszewski
2024-10-16 19:55 ` Mary Strodl
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=2024101314-rephrase-lark-c93a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mstrodl@csh.rit.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;
as well as URLs for NNTP newsgroup(s).