From: Johan Hovold <johan@kernel.org>
To: Karoly Pados <pados@pados.hu>
Cc: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Loic Poulain <loic.poulain@linaro.org>
Subject: Re: [PATCH v3] USB: serial: ftdi_sio: implement GPIO support for FT-X devices
Date: Tue, 18 Sep 2018 10:54:15 +0200 [thread overview]
Message-ID: <20180918085415.GB3943@localhost> (raw)
In-Reply-To: <538e77cf9622664f3e9d79a90269cf7d@pados.hu>
On Fri, Sep 14, 2018 at 04:54:34PM +0000, Karoly Pados wrote:
> >> +
> >> + /* Chip-type guessing logic based on libftdi. */
> >> + priv->gc.ngpio = 4; /* FT230X, FT231X */
> >> + if (le16_to_cpu(serial->dev->descriptor.bcdDevice) != 0x1000)
> >> + priv->gc.ngpio = 1; /* FT234XD */
> >
> > No known way to identify FT234XD here?
> >
> > After taking a quick peek at libftdi, it seems we really have no clue
> > how to detect these device types and 0x1000 could be for all FTX
> > devices. Heck, the current kernel driver just assumes anything we don't
> > recognise to be an FTX, something which would now hit this code path...
> >
> > What devices did you and Loic have? Could you post the lsusb -v output
> > for these? Perhaps someone with an FT234XD can chime in as well.
> >
>
> No clue about this one. I only own FT230X and FT231X devices, but it looks
> like they cannot be told apart, except for eeprom strings which are reconfigurable
> by the user. I wouldn't rely on such things. Anyway, lsusb -v outputs attached.
Ok, thanks. I've dropped a mail to FTDI support to see if there's way to
tell FT234XD apart from the other two. Otherwise we probably need to
register all four pins for all FTX devices.
It seems reasonable to assume that the FT234XD CBUS0 pin is indeed
managed as CBUS0 of the other two types (rather than say CBUS2), but I
asked for confirmation on that too.
Johan
prev parent reply other threads:[~2018-09-18 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 17:43 [PATCH v3] USB: serial: ftdi_sio: implement GPIO support for FT-X devices Karoly Pados
2018-09-14 16:11 ` Johan Hovold
2018-09-14 16:54 ` Karoly Pados
2018-09-18 8:54 ` Johan Hovold [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=20180918085415.GB3943@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=pados@pados.hu \
/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).