From: Johan Hovold <johan@kernel.org>
To: Ryan Mann <rmann@ndigital.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] NDI FTDI USB driver support
Date: Wed, 9 Jul 2025 11:54:05 +0200 [thread overview]
Message-ID: <aG48PYdWZXwbrd5S@hovoldconsulting.com> (raw)
In-Reply-To: <YQXPR01MB4987FF89C01297FA6F1B0C9FDF42A@YQXPR01MB4987.CANPRD01.PROD.OUTLOOK.COM>
On Fri, Jul 04, 2025 at 05:25:43PM +0000, Ryan Mann wrote:
> From: Ryan Mann (NDI) <rmann@ndigital.com>
>
> NDI (Northern Digital Inc.) is introducing a new product called the
> EMGUIDE GEMINI that will use an FTDI chip for USB serial communications.
> Remove the use of the baud rate mapping for NDI Aurora.
Your commit message should explain *why* a change is done.
This bit also looks like an unrelated change that should go in it's own
patch. It also no longer reflects what the patch does.
> Add the NDI VID definition as "FTDI_NDI_VID" into the ftdi_sio_ids.h.
> Add the NDI EMGUIDE GEMINI PID definition into the ftdi_sio_ids.h.
No need to be this specific, just say something about the adding the
device id which uses a new vendor define unlike the older products.
> Add the NDI VID/EMGUIDE GEMINI PID combination to the USB_DEVICE list.
Not needed.
> Signed-off-by: Ryan Mann <rmann@ndigital.com>
> ---
> V1 -> V2: Email-to issues fixed
> V2 -> V3: Email formatting issues fixed
> V3 -> V4: Email formatting issues fixed
You clearly left out some changes here since your initial submission
also added ids for "future" devices.
There was also some changes related to the two NID quirks.
> drivers/usb/serial/ftdi_sio.c | 4 ++--
> drivers/usb/serial/ftdi_sio_ids.h | 2 ++
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
> index 6ac7a0a5cf07..e5d7cce83a72 100644
> --- a/drivers/usb/serial/ftdi_sio.c
> +++ b/drivers/usb/serial/ftdi_sio.c
> @@ -801,8 +801,8 @@ static const struct usb_device_id id_table_combined[] = {
> .driver_info = (kernel_ulong_t)&ftdi_NDI_device_quirk },
> { USB_DEVICE(FTDI_VID, FTDI_NDI_FUTURE_3_PID),
> .driver_info = (kernel_ulong_t)&ftdi_NDI_device_quirk },
> - { USB_DEVICE(FTDI_VID, FTDI_NDI_AURORA_SCU_PID),
> - .driver_info = (kernel_ulong_t)&ftdi_NDI_device_quirk },
Why are you removing the old product from the id table which will
prevent the driver from binding to it?
> + { USB_DEVICE(NDI_VID, FTDI_NDI_EMGUIDE_GEMINI_PID),
> + .driver_info = (kernel_ulong_t)&ftdi_NDI_device_quirk },
Your patch is also white space damaged (e.g. tabs replaced with spaces,
which prevents it from being applied.
Try sending the patch to yourself first and make sure you can apply it
with git am.
> { USB_DEVICE(TELLDUS_VID, TELLDUS_TELLSTICK_PID) },
> { USB_DEVICE(NOVITUS_VID, NOVITUS_BONO_E_PID) },
> { USB_DEVICE(FTDI_VID, RTSYSTEMS_USB_VX8_PID) },
> diff --git a/drivers/usb/serial/ftdi_sio_ids.h b/drivers/usb/serial/ftdi_sio_ids.h
> index 9acb6f837327..0cb33d257973 100644
> --- a/drivers/usb/serial/ftdi_sio_ids.h
> +++ b/drivers/usb/serial/ftdi_sio_ids.h
> @@ -203,6 +203,8 @@
> #define FTDI_NDI_FUTURE_2_PID 0xDA72 /* NDI future device #2 */
> #define FTDI_NDI_FUTURE_3_PID 0xDA73 /* NDI future device #3 */
> #define FTDI_NDI_AURORA_SCU_PID 0xDA74 /* NDI Aurora SCU */
Please include a newline here to separate the two sections.
> +#define FTDI_NDI_VID 0x23F2 /* NDI Vendor ID */
And drop the comment here.
> +#define FTDI_NDI_EMGUIDE_GEMINI_PID 0x0003 /* NDI Emguide Gemini */
>
> /*
> * ChamSys Limited (www.chamsys.co.uk) USB wing/interface product IDs
Johan
prev parent reply other threads:[~2025-07-09 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 17:25 [PATCH v4] NDI FTDI USB driver support Ryan Mann
2025-07-09 9:54 ` Johan Hovold [this message]
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=aG48PYdWZXwbrd5S@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rmann@ndigital.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 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.