From: Martyn Welch <martyn.welch@collabora.co.uk>
To: Karl Palsson <karlp@tweak.net.au>
Cc: Alexandre Courbot <gnurou@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Johan Hovold <johan@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Linux USB Mailing List <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v4] USB: serial: cp210x: Adding GPIO support for CP2105
Date: Tue, 2 Feb 2016 10:45:55 +0000 [thread overview]
Message-ID: <56B088E3.7080603@collabora.co.uk> (raw)
In-Reply-To: <20160202103622-15241-91021-mailpile@palmtree-beeroclock-net>
On 02/02/16 10:41, Karl Palsson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Martyn Welch <martyn.welch@collabora.co.uk> wrote:
>>
>>
>>
>> The cp2105 is the only one of these devices that muxes GPIO
>> with serial control signals. The cp2102, cp2103 and cp2108
>> provide both GPIO and serial control signals separately, so the
>> logic to configure the GPIO for those devices will be much
>> simpler. (Hence why I called this cp210x_shared_gpio_init, as I
>> figured the best approach for supporting the other devices
>> would be through a separate init routine).
>>
>>> What about the other configurations supported for these pins (e.g.
>>> traffic indication, rs485, ...). Would you also end up with non-zero
>>> values for those?
>>>
>>
>> Will investigate.
>>
>
> CP2105 is configured by OTP rom, so should those options even be
> configurable? It's _very_ easy to blow through your settings
> trying to configure these. Especially given that cp2102 and
> cp2104 and cp2108 all have proper EEPROM for these settings. (And
> the "dual" ports aren't remotely equal, the cp2105 is a kinda
> ugly stepchild really)
>
I'm not trying to configure the device, however I do need to determine
how the device is configured to do the right thing.
Martyn
> Cheers,
> Karl P
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
>
> iQIcBAEBAgAGBQJWsIfxAAoJEBmotQ/U1cr2MZIQAKG+N/qiXbv0VYB3nglB/xss
> d9Jhx9BuCHFcMdxH/zKipqxn43v7/QRJvCdXNRYyDWWjbNvgi7VjqaGo+ywcgE9P
> KZxF3DgvUD0ybrrkEV2p9p7Gu2y2tGQazQLAKXAuRTmHRJnASasOVTEBXI8n7IR1
> oTO0WctaTITHl7cA7BcZe3oIN9E5XU1GLTqaOP5pWqwiz55xDbFUVHkfhq+psHPR
> X8P5Vn9yKWYWa4qw/Xg8p6SdW83sdlAIIN+XXrM8kHH1S3YHT0oi2KcDuIY4wsxD
> WkqnPnzsJG7yFTXcXqyEaV4s54ALsKTcFIIMLfP+O6H7OYD/BIxCbWa7RfBBB0ts
> tfml5cx7gfy7SUwmaZVs9hCbwQskx8jU2mnl685dbGQH6zAV4DfAPYQb3aYQxkP8
> B+klSwBPTptYvZLMiuvb9cUF6XpdQqDmdC820APAaEv1cl+uuqjtn2YkLlEv/JqV
> sZmkpiNH4yVwvTRcqOYtaMZbLndnXJaz667dkYGfEOO6njWFmYHy0MJBY8O1OKzO
> ZZtpoa6oAT6kmbF5DR0wUpl9hu7O423qogLngDYYP5jUZUwxQtvsSsdYRWfF+wCX
> FAcwzYVZ/EiyAU/jeyOZhxoMZ5+x6Ikze1Kb4KJJKvKnLJu57bHHGPsby0ZJPa6b
> tWxRfTEBA5limAc0NXSF
> =ZPkX
> -----END PGP SIGNATURE-----
>
next prev parent reply other threads:[~2016-02-02 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 14:14 [PATCH v4] USB: serial: cp210x: Adding GPIO support for CP2105 Martyn Welch
2016-01-31 19:54 ` Johan Hovold
2016-02-01 12:43 ` Martyn Welch
2016-02-02 10:41 ` Karl Palsson
2016-02-02 10:45 ` Martyn Welch [this message]
[not found] ` <56AF52E0.2080507-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2016-02-28 12:26 ` Johan Hovold
2016-03-24 18:01 ` Martyn Welch
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=56B088E3.7080603@collabora.co.uk \
--to=martyn.welch@collabora.co.uk \
--cc=gnurou@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=karlp@tweak.net.au \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).