From: David Heidelberg <david@ixit.cz>
To: johan@kernel.org, Corentin Labbe <clabbe@baylibre.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
gregkh@linuxfoundation.org
Subject: Re: [PATCH v6 0/2] usb: serial: add support for CH348
Date: Thu, 17 Aug 2023 01:34:35 +0200 [thread overview]
Message-ID: <799d01c6-e256-468b-a913-5945f22b5789@ixit.cz> (raw)
In-Reply-To: <20230628133834.1527941-1-clabbe@baylibre.com>
Hello Johan,
Any chance to get CH348 into 6.5?
I want to highlight that from all serials I have around this is the only
one which support 1500000 baud (needed for Rockchip devices).
Thank you!
David
On 28/06/2023 15:38, Corentin Labbe wrote:
> Hello
>
> The CH348 is an octo serial to USB adapter.
> The following patch adds a driver for supporting it.
> Since there is no public datasheet, unfortunatly it remains some magic values.
>
> It was tested with a large range of baud from 1200 to 1500000 and used with
> success in one of our kernel CI testlab.
>
> Regards
>
> Changes since v1:
> - use a data structure for encoding/decoding messages.
> - check if needed endpoints exists
> - fix URB leak in ch348_allocate_status_read error case
> - test for maximum baud rate as stated by datasheet
>
> Changes since v2:
> - specify ch348_rxbuf data length
> - Use correct speed_t dwDTERate instead of __le32
> - test for maximum baud rate supported according to datasheet
> - Use a define for CH348_TX_HDRSIZE
>
> Changes since v3
> - Fixed all reported problem from https://lore.kernel.org/lkml/Y5NDwEakGJbmB6+b@Red/T/#mb6234d0427cfdabf412190565e215995a41482dd
> Mostly reworked the endpoint mux to be the same than mx_uport
>
> Changes since v4:
> - The V4 was sent against stable and next have ch348_set_termios ktermios
> parameter const that I forgot to change
>
> Changes since v5:
> - Fixed all reported problem from https://lore.kernel.org/lkml/20230106135338.643951-1-clabbe@baylibre.com/T/#m044aab24dfb652ea34aa06f8ef704da9d6a2e036
> - Major change is dropping of all status handling which was unused.
> It will be probably necessary to bring it back when using GPIO.
> This will be done when I will finish my next devboard.
>
> Corentin Labbe (2):
> usb: serial: add support for CH348
> usb: serial: add myself as maintainer of CH348
>
> MAINTAINERS | 5 +
> drivers/usb/serial/Kconfig | 9 +
> drivers/usb/serial/Makefile | 1 +
> drivers/usb/serial/ch348.c | 491 ++++++++++++++++++++++++++++++++++++
> 4 files changed, 506 insertions(+)
> create mode 100644 drivers/usb/serial/ch348.c
>
--
David Heidelberg
Certified Linux Magician
next prev parent reply other threads:[~2023-08-16 23:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 13:38 Corentin Labbe
2023-06-28 13:38 ` [PATCH v6 1/2] " Corentin Labbe
2023-06-28 13:38 ` [PATCH v6 2/2] usb: serial: add myself as maintainer of CH348 Corentin Labbe
2023-07-01 19:16 ` [PATCH v6 0/2] usb: serial: add support for CH348 David Heidelberg
2023-08-16 23:34 ` David Heidelberg [this message]
2023-08-30 17:43 ` Nicolas Frattaroli
2023-09-27 12:09 ` David Heidelberg
2023-11-20 12:29 ` Corentin LABBE
2024-04-03 13:27 ` David Heidelberg
2024-04-10 20:04 ` Corentin LABBE
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=799d01c6-e256-468b-a913-5945f22b5789@ixit.cz \
--to=david@ixit.cz \
--cc=clabbe@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®