linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: "C. SB" <fenugrec-f9SIN1PjVWVBDgjK7y7TUQ@public.gmane.org>
Cc: linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: CH340/341: cannot open twice
Date: Sat, 19 Sep 2015 15:10:32 -0700	[thread overview]
Message-ID: <20150919221032.GF2360@localhost> (raw)
In-Reply-To: <trinity-deaddc67-9f42-4260-9032-d3eb30b7e8f1-1442696993994@3capp-mailcom-lxa06>

On Sat, Sep 19, 2015 at 11:09:54PM +0200, C. SB wrote:
> Hi,
> I'm having a strange issue with a CH340 usb-serial IC : I can only
> use/open it once. Here's what I try:

> The only solution is to unplug+replug the IC; any code using open()
> will fail with the same error.
> 
> lsusb output:
> Bus 002 Device 002: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
> 
> I tried only on kernels 4.0.6 and 4.1.6, system is archlinux x86-64.
> 
> Am I alone having this problem ?

I'm afraid not. There has been a couple of reports of problem with this
device. The reported problems have looked like hardware issues, but it
now seems like support for these devices is simply lacking in the
driver.

Could you try the vendor driver and see if that makes the device work so
that we'd know for sure?

Thanks,
Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

       reply	other threads:[~2015-09-19 22:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <trinity-deaddc67-9f42-4260-9032-d3eb30b7e8f1-1442696993994@3capp-mailcom-lxa06>
2015-09-19 22:10 ` Johan Hovold [this message]
     [not found]   ` <trinity-efc5f19e-b3a1-4cc7-b944-04deb6368aca-1442710334176@3capp-mailcom-lxa02>
2015-09-20 20:56     ` CH340/341: cannot open twice Johan Hovold

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=20150919221032.GF2360@localhost \
    --to=johan-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=fenugrec-f9SIN1PjVWVBDgjK7y7TUQ@public.gmane.org \
    --cc=linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).