linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Patong Yang <patong.mxl@gmail.com>
Cc: johan@kernel.org, pyang@maxlinear.com, linux-usb@vger.kernel.org
Subject: Driver for MaxLinear/Exar USB (UART) Serial adapters.
Date: Thu, 5 Apr 2018 08:26:54 +0200	[thread overview]
Message-ID: <20180405062654.GA5078@kroah.com> (raw)

On Wed, Apr 04, 2018 at 12:03:51PM -0700, Patong Yang wrote:
> Thanks for the quick reply and feedback.  This needs to be a different
> driver because although the USB UARTs can work with the CDC-ACM driver,
> there are limitations in the CDC-ACM spec and therefore the driver that
> prevents it from fully functioning as a standard serial port (ie. status of
> CTS pin, ability to enable/disable flow control).  Therefore, the USB UARTs
> also support custom USB Vendor requests so that it can behave as a standard
> serial port and support other device features such as GPIO control and the
> automatic direction control feature typically used in RS-485 and RS-422
> designs.

The GPIO stuff needs to be a separate interface, using the kernel's GPIO
api, not custom ioctls.

> The USB device can describe itself properly.  The SMBIOS function is a
> requirement from our customer who designed a board using our device where
> their CPU reads from a specific BIOS location and initializes GPIOs based
> on the settings.  These GPIOs set the mode of the transceiver (LOOPBACK,
> RS232, RS485, or RS422).  Therefore, the driver also reads the same
> settings from the BIOS, so that it can enable the appropriate mode.

That logic can be done in userspace, no need to do that within the
kernel, right?

> This same customer is designing a new board to support the same transceiver
> configurations.  Instead of using the BIOS settings, they would like to use
> a user-space application to configure the additional GPIOs in a newer USB
> UART to set the transceiver modes, however, there are no standard APIs to
> support setting different modes, hence the custom IOCTLs.

What is wrong with the current GPIO Linux api?  Doesn't that support
everything you need here?

thanks,

greg k-h
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2018-04-05  6:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05  6:26 Greg Kroah-Hartman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-08-16 10:05 Driver for MaxLinear/Exar USB (UART) Serial Adapters Greg Kroah-Hartman
2018-08-16  8:28 Patong Yang
2018-08-16  8:26 Oliver Neukum
2018-08-16  6:34 Greg Kroah-Hartman
2018-08-16  5:56 Patong Yang
2018-07-26 10:57 Greg Kroah-Hartman
2018-07-25  7:38 Oliver Neukum
2018-07-24 22:36 Patong Yang
2018-04-06 14:45 Driver for MaxLinear/Exar USB (UART) Serial adapters Greg Kroah-Hartman
2018-04-05  7:38 Oliver Neukum
2018-04-04  8:00 Greg Kroah-Hartman
2018-04-04  7:59 Greg Kroah-Hartman
2018-04-04  7:38 Oliver Neukum
2018-04-04  7:06 Patong Yang

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=20180405062654.GA5078@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=patong.mxl@gmail.com \
    --cc=pyang@maxlinear.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;
as well as URLs for NNTP newsgroup(s).