>> On Di, 2019-03-19 at 11:36 +0100, Johan Hovold wrote:
>> On Mon, Feb 18, 2019 at 10:17:12AM +0100, Oliver Neukum wrote:
>>> On So, 2019-02-17 at 18:59 +0100, Karoly Pados wrote:
Current GPIO code in cp210x fails to take USB autosuspend into account,
making it practically impossible to
On Tue, Mar 19, 2019 at 12:15:06PM +0100, Oliver Neukum wrote:
> On Di, 2019-03-19 at 11:36 +0100, Johan Hovold wrote:
> > On Mon, Feb 18, 2019 at 10:17:12AM +0100, Oliver Neukum wrote:
> > > On So, 2019-02-17 at 18:59 +0100, Karoly Pados wrote:
> > > > Current GPIO code in cp210x fails to take USB
On Sun, Feb 17, 2019 at 06:59:01PM +0100, Karoly Pados wrote:
> Current GPIO code in cp210x fails to take USB autosuspend into account,
> making it practically impossible to use GPIOs with autosuspend enabled
> without user configuration. Fix this like for ftdi_sio in a previous patch.
> Tested on
On So, 2019-02-17 at 18:59 +0100, Karoly Pados wrote:
> Current GPIO code in cp210x fails to take USB autosuspend into account,
> making it practically impossible to use GPIOs with autosuspend enabled
> without user configuration. Fix this like for ftdi_sio in a previous patch.
> Tested on a CP2102
Current GPIO code in cp210x fails to take USB autosuspend into account,
making it practically impossible to use GPIOs with autosuspend enabled
without user configuration. Fix this like for ftdi_sio in a previous patch.
Tested on a CP2102N.
Signed-off-by: Karoly Pados
---
Changelog:
- v2: Restrict
5 matches
Mail list logo