From: Manivannan Sadhasivam <mani@kernel.org>
To: gregkh@linuxfoundation.org
Cc: johan@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, patong.mxl@gmail.com,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH 2/2] usb: serial: xr_serial: Add gpiochip support
Date: Wed, 29 Apr 2020 23:17:27 +0530 [thread overview]
Message-ID: <20200429174727.GF6443@Mani-XPS-13-9360> (raw)
In-Reply-To: <20200428195651.6793-3-mani@kernel.org>
Hi Greg,
On Wed, Apr 29, 2020 at 01:26:51AM +0530, mani@kernel.org wrote:
> From: Manivannan Sadhasivam <mani@kernel.org>
>
> Add gpiochip support for Maxlinear/Exar USB to serial converter
> for controlling the available gpios.
>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Cc: linux-gpio@vger.kernel.org
> Signed-off-by: Manivannan Sadhasivam <mani@kernel.org>
> ---
> drivers/usb/serial/xr_serial.c | 186 ++++++++++++++++++++++++++++++++-
> drivers/usb/serial/xr_serial.h | 7 ++
> 2 files changed, 192 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/serial/xr_serial.c b/drivers/usb/serial/xr_serial.c
> index ea4a0b167d3f..d86fd40839f8 100644
> --- a/drivers/usb/serial/xr_serial.c
> +++ b/drivers/usb/serial/xr_serial.c
> @@ -476,6 +476,189 @@ static void xr_break_ctl(struct tty_struct *tty, int break_state)
> state);
> }
>
> +#ifdef CONFIG_GPIOLIB
> +
[...]
> +
> +static int xr_gpio_init(struct usb_serial_port *port)
> +{
> + struct xr_port_private *port_priv = usb_get_serial_port_data(port);
> + int ret = 0;
> +
> + if (port_priv->idProduct == XR21V141X_ID)
> + ret = xr21v141x_gpio_init(port);
> +
> + if (ret < 0)
> + return ret;
> +
> + port_priv->gc.label = "xr_gpios";
> + port_priv->gc.request = xr_gpio_request;
> + port_priv->gc.get_direction = xr_gpio_direction_get;
> + port_priv->gc.direction_input = xr_gpio_direction_input;
> + port_priv->gc.direction_output = xr_gpio_direction_output;
> + port_priv->gc.get = xr_gpio_get;
> + port_priv->gc.set = xr_gpio_set;
> + port_priv->gc.owner = THIS_MODULE;
> + port_priv->gc.parent = &port->dev;
> + port_priv->gc.base = -1;
> + port_priv->gc.can_sleep = true;
> +
> + ret = gpiochip_add_data(&port_priv->gc, port);
> + if (!ret)
> + port_priv->gpio_registered = true;
> +
> + return ret;
> +}
> +
> +static void xr_gpio_remove(struct usb_serial_port *port)
> +{
> + struct xr_port_private *port_priv = usb_get_serial_port_data(port);
> +
> + if (port_priv->gpio_registered) {
> + gpiochip_remove(&port_priv->gc);
> + port_priv->gpio_registered = false;
> + }
> +}
> +
> +#else
> +
> +static int xr_gpio_init(struct usb_serial_port *port)
> +{
> + return 0;
> +}
> +
> +static void xr_gpio_remove(struct usb_serial_port *port)
> +{
> + /* Nothing to do */
> +}
> +
> +#endif
> +
> static int xr_port_probe(struct usb_serial_port *port)
> {
> struct usb_serial *serial = port->serial;
> @@ -495,13 +678,14 @@ static int xr_port_probe(struct usb_serial_port *port)
>
> usb_set_serial_port_data(port, port_priv);
>
> - return 0;
> + return xr_gpio_init(port);
Just realised that the gpiochip is registered for 2 interfaces exposed by
this chip. This is due to the fact that this chip presents CDC-ACM model,
so there are 2 interfaces (interrupt and bulk IN/OUT).
We shouldn't need gpiochip for interface 0. So what is the recommended way
to filter that?
Thanks,
Mani
> }
>
> static int xr_port_remove(struct usb_serial_port *port)
> {
> struct xr_port_private *port_priv = usb_get_serial_port_data(port);
>
> + xr_gpio_remove(port);
> kfree(port_priv);
>
> return 0;
> diff --git a/drivers/usb/serial/xr_serial.h b/drivers/usb/serial/xr_serial.h
> index d2977ef847a0..079098cf553a 100644
> --- a/drivers/usb/serial/xr_serial.h
> +++ b/drivers/usb/serial/xr_serial.h
> @@ -3,6 +3,8 @@
> #ifndef __LINUX_USB_SERIAL_XR_SERIAL_H
> #define __LINUX_USB_SERIAL_XR_SERIAL_H
>
> +#include <linux/gpio/driver.h>
> +
> struct xr_uart_regs {
> u8 enable;
> u8 format;
> @@ -21,6 +23,11 @@ struct xr_uart_regs {
> };
>
> struct xr_port_private {
> +#ifdef CONFIG_GPIOLIB
> + struct gpio_chip gc;
> + bool gpio_registered;
> + u8 gpio_altfunc;
> +#endif
> const struct xr_uart_regs *regs;
> u16 idProduct;
> u8 reg_width;
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-04-29 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200428195651.6793-1-mani@kernel.org>
2020-04-28 19:56 ` [PATCH 2/2] usb: serial: xr_serial: Add gpiochip support mani
2020-04-29 12:12 ` Linus Walleij
2020-04-29 12:49 ` Manivannan Sadhasivam
2020-05-19 8:57 ` Johan Hovold
2020-05-25 8:59 ` Linus Walleij
2020-05-25 11:12 ` Greg KH
2020-05-25 13:02 ` Linus Walleij
2020-05-25 13:35 ` Greg KH
2020-04-29 17:47 ` Manivannan Sadhasivam [this message]
2020-04-29 17:59 ` Greg KH
2020-05-19 9:08 ` Johan Hovold
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=20200429174727.GF6443@Mani-XPS-13-9360 \
--to=mani@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=patong.mxl@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