From: Crescent CY Hsieh <crescentcy.hsieh@moxa.com>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH 3/6] tty: mxser: serial: 8250: Relocate device IDs from mxser to 8250_pci
Date: Thu, 13 Jun 2024 18:03:03 +0800 [thread overview]
Message-ID: <ZmrD1wZGha9aC+Ri@localhost.localdomain> (raw)
In-Reply-To: <0d8da651-4e41-4af2-81cc-732f17aab403@kernel.org>
On Tue, Jun 11, 2024 at 09:42:36AM +0200, Jiri Slaby wrote:
> On 07. 06. 24, 13:43, Crescent Hsieh wrote:
> > @@ -212,32 +187,7 @@ static const struct {
> > /* driver_data correspond to the lines in the structure above
> > see also ISA probe function before you change something */
> > static const struct pci_device_id mxser_pcibrds[] = {
> > - { PCI_DEVICE_DATA(MOXA, C168, 8) },
> > - { PCI_DEVICE_DATA(MOXA, C104, 4) },
> > - { PCI_DEVICE_DATA(MOXA, CP132, 2) },
> > - { PCI_DEVICE_DATA(MOXA, CP114, 4) },
> > - { PCI_DEVICE_DATA(MOXA, CT114, 4) },
> > - { PCI_DEVICE_DATA(MOXA, CP102, 2 | MXSER_HIGHBAUD) },
>
> How is this MXSER_HIGHBAUD handled in 8250_pci?
I will first create a patch to split the Moxa-related code from
`8250_pci.c` into `8250_moxa.c`. Then, I will try to migrate `mxser.c`
to `8250_moxa.c` and handle MXSER_HIGHBAUD there.
>
> > - { PCI_DEVICE_DATA(MOXA, CP104U, 4) },
> > - { PCI_DEVICE_DATA(MOXA, CP168U, 8) },
> > - { PCI_DEVICE_DATA(MOXA, CP132U, 2) },
> > - { PCI_DEVICE_DATA(MOXA, CP134U, 4) },
> > - { PCI_DEVICE_DATA(MOXA, CP104JU, 4) },
> > { PCI_DEVICE_DATA(MOXA, RC7000, 8) }, /* RC7000 */
>
> Can you simply add this exception to mxser_get_nports() I suggested in 1/6
> and drop the whole mxser then \o/?
>
> I had a long-term plan to mount mxser onto serial-core (or 8250). I haven't
> managed the conversion yet. So I am glad to see this.
Yes, I know you have been working hard to convert `mxser.c` into a
general driver, and I truly appreciate your efforts.
https://lore.kernel.org/linux-serial/20210618061516.662-1-jslaby@suse.cz/
However, I am curious if a general serial driver can support the full
functionality of PCI serial boards. Additionally, what's the plans for
addressing specific functionalities?
---
Sincerely,
Crescent Hsieh
next prev parent reply other threads:[~2024-06-13 10:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 11:43 [PATCH 0/6] Adjustments and Enhancements for MOXA PCI Serial Boards Crescent Hsieh
2024-06-07 11:43 ` [PATCH 1/6] tty: serial: 8250: Fix the amount of ports doesn't match the device Crescent Hsieh
2024-06-08 9:58 ` Andy Shevchenko
2024-06-11 7:39 ` Jiri Slaby
2024-06-07 11:43 ` [PATCH 2/6] tty: serial: 8250: Add 2 ports PCI configuration for 921600 BAR 2 Crescent Hsieh
2024-06-07 11:43 ` [PATCH 3/6] tty: mxser: serial: 8250: Relocate device IDs from mxser to 8250_pci Crescent Hsieh
2024-06-11 7:42 ` Jiri Slaby
2024-06-13 10:03 ` Crescent CY Hsieh [this message]
2024-06-07 11:43 ` [PATCH 4/6] tty: serial: 8250: Add check for setting default serial interface Crescent Hsieh
2024-06-08 9:57 ` Andy Shevchenko
2024-06-07 11:43 ` [PATCH 5/6] tty: serial: 8250: Add support for Moxa PCIe boards to switch interface Crescent Hsieh
2024-06-08 9:51 ` Andy Shevchenko
2024-06-07 11:43 ` [PATCH 6/6] tty: serial: 8250: Add support for MUEX50 UART Crescent Hsieh
2024-06-08 9:52 ` Andy Shevchenko
2024-06-08 9:47 ` [PATCH 0/6] Adjustments and Enhancements for MOXA PCI Serial Boards Andy Shevchenko
2024-06-13 10:15 ` Crescent CY Hsieh
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=ZmrD1wZGha9aC+Ri@localhost.localdomain \
--to=crescentcy.hsieh@moxa.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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