From: Greg KH <gregkh@linuxfoundation.org>
To: Jan-Niklas Burfeind <kernel@aiyionpri.me>,
Dmytro Bagrii <dimich.dmb@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH] Revert "USB: serial: ch341: add new Product ID for CH341A"
Date: Tue, 8 Feb 2022 11:34:44 +0100 [thread overview]
Message-ID: <YgJHRKQHQheKTwjU@kroah.com> (raw)
In-Reply-To: <20220207000822.697343-1-dimich.dmb@gmail.com>
On Mon, Feb 07, 2022 at 02:08:23AM +0200, Dmytro Bagrii wrote:
> This reverts commit 46ee4abb10a07bd8f8ce910ee6b4ae6a947d7f63.
You forgot to cc: the author of that commit, why?
Also forgot to cc: the maintainer of the driver/subsytem?
> CH341A has three different modes of operation selectable either by
> hardware pin connections or by external EEPROM configuration. Each
> mode is represented by corresponding product ID:
>
> 0x5523: Asyncronous Serial Interface
> 0x5584: Parallel Printer Interface
> 0x5512: EPP/MEM Interface
That does not corrispond with what Jan-Niklas said in the original
commit.
>
> (See "5.3.Function configuration" in datasheet at wch-ic.com/downloads/CH341DS1_PDF.html)
>
> When CH341A is configured as EPP/MEM Interface it appears as 1a86:5512 and being mistakenly
> handled by ch341 USB serial driver.
>
> It is possible to use CH341A in EPP/MEM mode only if ch341 module is blacklisted, but it must be
> unblacklisted every time to use CH341A as a serial converter. Also obviously it is impossible
> to use two CH341A boards in different modes simoultaneously.
Please wrap your lines at 72 columns.
thanks,
greg k-h
next prev parent reply other threads:[~2022-02-08 11:32 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 [this message]
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
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=YgJHRKQHQheKTwjU@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dimich.dmb@gmail.com \
--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.