From: Johan Hovold <johan@kernel.org>
To: Himadri Pandya <himadrispandya@gmail.com>
Cc: johan@kernel.org, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH 15/15] usb: serial: kl5kusb105: use usb_control_msg_recv() and usb_control_msg_send()
Date: Fri, 4 Dec 2020 11:37:33 +0100 [thread overview]
Message-ID: <X8oRbaWuSoZSRAT8@localhost> (raw)
In-Reply-To: <20201104064703.15123-16-himadrispandya@gmail.com>
On Wed, Nov 04, 2020 at 12:17:03PM +0530, Himadri Pandya wrote:
> The new usb_control_msg_recv() and usb_control_msg_send() nicely wraps
> usb_control_msg() with proper error check. Hence use the wrappers
> instead of calling usb_control_msg() directly
>
> Signed-off-by: Himadri Pandya <himadrispandya@gmail.com>
> ---
> drivers/usb/serial/kl5kusb105.c | 94 +++++++++++++++------------------
> 1 file changed, 44 insertions(+), 50 deletions(-)
>
> diff --git a/drivers/usb/serial/kl5kusb105.c b/drivers/usb/serial/kl5kusb105.c
> index 5ee48b0650c4..75cfd1c907f3 100644
> --- a/drivers/usb/serial/kl5kusb105.c
> +++ b/drivers/usb/serial/kl5kusb105.c
> @@ -124,16 +124,17 @@ static int klsi_105_chg_port_settings(struct usb_serial_port *port,
> {
> int rc;
>
> - rc = usb_control_msg(port->serial->dev,
> - usb_sndctrlpipe(port->serial->dev, 0),
> - KL5KUSB105A_SIO_SET_DATA,
> - USB_TYPE_VENDOR | USB_DIR_OUT | USB_RECIP_INTERFACE,
> - 0, /* value */
> - 0, /* index */
> - settings,
> - sizeof(struct klsi_105_port_settings),
> - KLSI_TIMEOUT);
> - if (rc < 0)
> + rc = usb_control_msg_send(port->serial->dev, 0,
> + KL5KUSB105A_SIO_SET_DATA,
> + USB_TYPE_VENDOR | USB_DIR_OUT |
> + USB_RECIP_INTERFACE,
> + 0, /* value */
> + 0, /* index */
> + settings,
> + sizeof(struct klsi_105_port_settings),
> + KLSI_TIMEOUT,
> + GFP_KERNEL);
> + if (rc)
> dev_err(&port->dev,
> "Change port settings failed (error = %d)\n", rc);
The callers of this function already allocates a transfer-buffer which
you should now remove to avoid introducing an additional memdup() per
call.
Note that there was a related bug in open() which failed to release it's
transfer buffer on successful open. I CCed you on the fix which we
should get merged and backported before converting to using the new
helper.
> @@ -283,16 +276,17 @@ static int klsi_105_open(struct tty_struct *tty, struct usb_serial_port *port)
> goto err_free_cfg;
> }
>
> - rc = usb_control_msg(port->serial->dev,
> - usb_sndctrlpipe(port->serial->dev, 0),
> - KL5KUSB105A_SIO_CONFIGURE,
> - USB_TYPE_VENDOR|USB_DIR_OUT|USB_RECIP_INTERFACE,
> - KL5KUSB105A_SIO_CONFIGURE_READ_ON,
> - 0, /* index */
> - NULL,
> - 0,
> - KLSI_TIMEOUT);
> - if (rc < 0) {
> + rc = usb_control_msg_send(port->serial->dev, 0,
> + KL5KUSB105A_SIO_CONFIGURE,
> + USB_TYPE_VENDOR | USB_DIR_OUT |
> + USB_RECIP_INTERFACE,
> + KL5KUSB105A_SIO_CONFIGURE_READ_ON,
> + 0, /* index */
> + NULL,
> + 0,
> + KLSI_TIMEOUT,
> + GFP_KERNEL);
> + if (rc) {
And again there's no need to change the control transfers without a data
stage.
Johan
next prev parent reply other threads:[~2020-12-04 10:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 6:46 [PATCH 00/15] usb: serial: avoid using usb_control_msg() directly Himadri Pandya
2020-11-04 6:46 ` [PATCH 01/15] usb: serial: ark3116: use usb_control_msg_recv() and usb_control_msg_send() Himadri Pandya
2020-12-04 9:16 ` Johan Hovold
2020-11-04 6:46 ` [PATCH 02/15] usb: serial: belkin_sa: use usb_control_msg_send() Himadri Pandya
2020-12-04 9:17 ` Johan Hovold
2020-11-04 6:46 ` [PATCH 03/15] usb: serial: ch314: use usb_control_msg_recv() and usb_control_msg_send() Himadri Pandya
2020-12-04 9:24 ` Johan Hovold
2020-11-04 6:46 ` [PATCH 04/15] usb: serial: cp210x: " Himadri Pandya
2020-12-04 9:34 ` Johan Hovold
2020-11-04 6:46 ` [PATCH 05/15] usb: serial: cypress_m8: " Himadri Pandya
2020-12-04 9:37 ` Johan Hovold
2020-11-04 6:46 ` [PATCH 06/15] usb: serial: f81232: " Himadri Pandya
2020-12-04 9:49 ` Johan Hovold
2020-11-04 6:46 ` [PATCH 07/15] usb: serial: f81534: " Himadri Pandya
2020-12-04 9:55 ` Johan Hovold
2020-11-04 6:46 ` [PATCH 08/15] usb: serial: ftdi_sio: " Himadri Pandya
2020-12-04 10:03 ` Johan Hovold
2020-11-04 6:46 ` [PATCH 09/15] usb: serial: io_edgeport: " Himadri Pandya
2020-12-04 10:10 ` Johan Hovold
2020-11-04 6:46 ` [PATCH 10/15] usb: serial: io_ti: " Himadri Pandya
2020-12-04 10:12 ` Johan Hovold
2020-11-04 6:46 ` [PATCH 11/15] usb: serial: ipaq: use usb_control_msg_send() Himadri Pandya
2020-12-04 10:21 ` Johan Hovold
2020-11-04 6:47 ` [PATCH 12/15] usb: serial: ipw: " Himadri Pandya
2020-12-04 10:27 ` Johan Hovold
2020-11-04 6:47 ` [PATCH 13/15] usb: serial: iuu_phoenix: " Himadri Pandya
2020-12-04 10:28 ` Johan Hovold
2020-11-04 6:47 ` [PATCH 14/15] usb: serial: keyspan_pda: use usb_control_msg_recv() and usb_control_msg_send() Himadri Pandya
2020-12-04 10:31 ` Johan Hovold
2020-11-04 6:47 ` [PATCH 15/15] usb: serial: kl5kusb105: " Himadri Pandya
2020-12-04 10:37 ` Johan Hovold [this message]
2020-11-06 10:43 ` [PATCH 00/15] usb: serial: avoid using usb_control_msg() directly Greg KH
2020-12-04 9:09 ` Johan Hovold
2020-12-24 10:01 ` Himadri Pandya
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=X8oRbaWuSoZSRAT8@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=himadrispandya@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).