From: Jiri Slaby <jirislaby@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Cameron Williams <cang1@live.co.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Fenghua Yu <fenghua.yu@intel.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-pci@vger.kernel.org
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH v1 2/2] serial: 8250_pci: Share WCH IDs with parport_serial driver
Date: Wed, 4 Dec 2024 08:14:42 +0100 [thread overview]
Message-ID: <5ca95d14-84a7-48af-a5e3-cefc558d2e7f@kernel.org> (raw)
In-Reply-To: <20241204031114.1029882-3-andriy.shevchenko@linux.intel.com>
On 04. 12. 24, 4:09, Andy Shevchenko wrote:
> parport_serial driver uses subset of WCH IDs that are present in 8250_pci.
> Share them via pci_ids.h and switch parport_serial to use defined constants.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/parport/parport_serial.c | 12 ++++++++----
> drivers/tty/serial/8250/8250_pci.c | 10 ++--------
> include/linux/pci_ids.h | 11 +++++++++++
> 3 files changed, 21 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/parport/parport_serial.c b/drivers/parport/parport_serial.c
> index 3644997a8342..24d4f3a3ec3d 100644
> --- a/drivers/parport/parport_serial.c
> +++ b/drivers/parport/parport_serial.c
> @@ -266,10 +266,14 @@ static struct pci_device_id parport_serial_pci_tbl[] = {
> { 0x1409, 0x7168, 0x1409, 0xd079, 0, 0, timedia_9079c },
>
> /* WCH CARDS */
> - { 0x4348, 0x5053, PCI_ANY_ID, PCI_ANY_ID, 0, 0, wch_ch353_1s1p},
> - { 0x4348, 0x7053, 0x4348, 0x3253, 0, 0, wch_ch353_2s1p},
> - { 0x1c00, 0x3050, 0x1c00, 0x3050, 0, 0, wch_ch382_0s1p},
> - { 0x1c00, 0x3250, 0x1c00, 0x3250, 0, 0, wch_ch382_2s1p},
> + { PCI_VENDOR_ID_WCHCN, PCI_DEVICE_ID_WCHCN_CH353_1S1P,
> + PCI_ANY_ID, PCI_ANY_ID, 0, 0, wch_ch353_1s1p },
> + { PCI_VENDOR_ID_WCHCN, PCI_DEVICE_ID_WCHCN_CH353_2S1P,
> + 0x4348, 0x3253, 0, 0, wch_ch353_2s1p },
> + { PCI_VENDOR_ID_WCHIC, PCI_DEVICE_ID_WCHIC_CH382_0S1P,
> + 0x1c00, 0x3050, 0, 0, wch_ch382_0s1p },
> + { PCI_VENDOR_ID_WCHIC, PCI_DEVICE_ID_WCHIC_CH382_2S1P,
> + 0x1c00, 0x3250, 0, 0, wch_ch382_2s1p },
I know this is the current pattern in the file. But what about using
PCI_DEVICE_DATA() for the first and PCI_DEVICE_SUB() + .driver_data for
the rest? Otherwise it occurs as a load of incomprehensible constants.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2024-12-04 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 3:09 [PATCH v1 0/2] serial: 8250_pci: Share WCH IDs Andy Shevchenko
2024-12-04 3:09 ` [PATCH v1 1/2] serial: 8250_pci: Resolve WCH vendor ID ambiguity Andy Shevchenko
2024-12-04 3:09 ` [PATCH v1 2/2] serial: 8250_pci: Share WCH IDs with parport_serial driver Andy Shevchenko
2024-12-04 7:14 ` Jiri Slaby [this message]
2024-12-04 9:53 ` Andy Shevchenko
2024-12-04 22:08 ` Bjorn Helgaas
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=5ca95d14-84a7-48af-a5e3-cefc558d2e7f@kernel.org \
--to=jirislaby@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=cang1@live.co.uk \
--cc=fenghua.yu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
/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