All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Dmytro Bagrii <dimich.dmb@gmail.com>
Cc: Jan-Niklas Burfeind <kernel@aiyionpri.me>,
	Greg KH <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org,
	Frank A Kingswood <frank@kingswood-consulting.co.uk>,
	Frank Zago <frank@zago.net>
Subject: Re: [PATCH] Revert "USB: serial: ch341: add new Product ID for CH341A"
Date: Mon, 21 Feb 2022 09:48:04 +0100	[thread overview]
Message-ID: <YhNRxJpRMamUIiu5@hovoldconsulting.com> (raw)
In-Reply-To: <02efa491-39fe-e4f3-d617-a6f17ceba6a5@gmail.com>

On Thu, Feb 10, 2022 at 07:41:22AM +0200, Dmytro Bagrii wrote:
> On 09.02.22 16:18, Johan Hovold wrote:

> > I don't remember all the details, but judging from a quick look it seems
> > we're just waiting for someone to resend the revert with a proper
> > explanation.
> > 
> > It would be good if Jan-Niklas could chime in too and confirm if he's
> > able to use the device in UART mode instead.
> 
> I'd like to take a look at that keeyees device from original commit 
> message to see if it has EEPROM chip. I can hypothesize that some 
> manufacturer of a CH341-based programmer could use external configuration 
> EEPROM and mixed-up PID value. I haven't experiment with configuring 
> CH341A with EEPROM but suppose it's possible to burn any custom VID:PID 
> there. I don't think ch341 driver has to handle any of such custom 
> VID/PID, especially if it conflicts with an original VID/PID assigned by 
> chip manufacturer. In case of some peculiar devices it's possible to bind 
> custom VID:PID to the driver via sysfs.
> 
> But it's just my hypothetical assumption how ch341-based device with PID 
> 5512 could work as UART in that case.
> 
> I just checked if CH341 that i have can work as UART when configured as 
> I2C/SPI (PID 5512). I doesn't work: no output signal on TX pin, no 
> loopback echo when RX connected to self TX.

Thanks for confirming.

Johan

  reply	other threads:[~2022-02-21  8:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07  0:08 [PATCH] Revert "USB: serial: ch341: add new Product ID for CH341A" Dmytro Bagrii
2022-02-08 10:34 ` Greg KH
2022-02-08 13:34   ` Dmytro Bagrii
2022-02-09 14:18     ` Johan Hovold
2022-02-09 17:24       ` Jan-Niklas Burfeind
2022-02-10  5:41       ` Dmytro Bagrii
2022-02-21  8:48         ` Johan Hovold [this message]
2022-02-10 10:18       ` Jan-Niklas Burfeind
2022-02-21  8:49         ` Johan Hovold
2022-02-10 16:41   ` [PATCH v2] " Dmytro Bagrii
2022-02-21  9:02     ` 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=YhNRxJpRMamUIiu5@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=dimich.dmb@gmail.com \
    --cc=frank@kingswood-consulting.co.uk \
    --cc=frank@zago.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@aiyionpri.me \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.