Date: Thu, 19 Feb 2015 12:50:47 +0700
From: Johan Hovold <johan@kernel.org>
To: Jari Ruusu <jariruusu@users.sourceforge.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, linux-usb@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: usb serial: pl2303 driver TxD "break" stays after close() bug
Message-ID: <20150219055047.GJ12405@localhost>
References: <CACMCwJJzOG=diSwDW3yg6zsfwQjTVRjV+9f3S5UHp6Or-meZWQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACMCwJJzOG=diSwDW3yg6zsfwQjTVRjV+9f3S5UHp6Or-meZWQ@mail.gmail.com>
User-Agent: Mutt/1.5.22 (2013-10-16)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 880
Lines: 19

On Thu, Feb 05, 2015 at 12:56:20PM +0200, Jari Ruusu wrote:
> Tested on 3.10.67 and 3.18.5 kernels with ATEN UC-232A usb-serial adapter.
> No patch, sorry. To actually see the stuck "break" signal on TxD line, you
> need either some sort of LED or voltmeter connected to the data transmit
> line. Other RS-232 serial ports that I have access to (normal PC hardware
> serial ports and FTDI usb-serial adapters) do not have this bug.

Thanks for the report. I believe you may be right here, but I'm not able
to verify this until earliest next week.

What happens when you reopen the port? Is the break state cleared then?

Thanks,
Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/