From: Johan Hovold <johan@kernel.org>
To: Himadri Pandya <himadrispandya@gmail.com>
Cc: linux-usb@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org, johan@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-kernel-mentees] [PATCH 03/15] usb: serial: ch314: use usb_control_msg_recv() and usb_control_msg_send()
Date: Fri, 4 Dec 2020 10:24:25 +0100 [thread overview]
Message-ID: <X8oASVHmeoCmM5RM@localhost> (raw)
In-Reply-To: <20201104064703.15123-4-himadrispandya@gmail.com>
On Wed, Nov 04, 2020 at 12:16:51PM +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/ch341.c | 45 ++++++++++++--------------------------
> 1 file changed, 14 insertions(+), 31 deletions(-)
>
> diff --git a/drivers/usb/serial/ch341.c b/drivers/usb/serial/ch341.c
> index a2e2f56c88cd..58c5d3ce4f75 100644
> --- a/drivers/usb/serial/ch341.c
> +++ b/drivers/usb/serial/ch341.c
> @@ -111,10 +111,10 @@ static int ch341_control_out(struct usb_device *dev, u8 request,
> dev_dbg(&dev->dev, "%s - (%02x,%04x,%04x)\n", __func__,
> request, value, index);
>
> - r = usb_control_msg(dev, usb_sndctrlpipe(dev, 0), request,
> - USB_TYPE_VENDOR | USB_RECIP_DEVICE | USB_DIR_OUT,
> - value, index, NULL, 0, DEFAULT_TIMEOUT);
> - if (r < 0)
> + r = usb_control_msg_send(dev, 0, request, USB_TYPE_VENDOR |
> + USB_RECIP_DEVICE | USB_DIR_OUT, value, index,
> + NULL, 0, DEFAULT_TIMEOUT, GFP_KERNEL);
> + if (r)
> dev_err(&dev->dev, "failed to send control message: %d\n", r);
>
> return r;
> @@ -129,23 +129,14 @@ static int ch341_control_in(struct usb_device *dev,
> dev_dbg(&dev->dev, "%s - (%02x,%04x,%04x,%u)\n", __func__,
> request, value, index, bufsize);
>
> - r = usb_control_msg(dev, usb_rcvctrlpipe(dev, 0), request,
> - USB_TYPE_VENDOR | USB_RECIP_DEVICE | USB_DIR_IN,
> - value, index, buf, bufsize, DEFAULT_TIMEOUT);
> - if (r < (int)bufsize) {
> - if (r >= 0) {
> - dev_err(&dev->dev,
> - "short control message received (%d < %u)\n",
> - r, bufsize);
> - r = -EIO;
> - }
> -
> + r = usb_control_msg_recv(dev, 0, request, USB_TYPE_VENDOR |
> + USB_RECIP_DEVICE | USB_DIR_IN, value, index,
> + buf, bufsize, DEFAULT_TIMEOUT, GFP_KERNEL);
> + if (r)
> dev_err(&dev->dev, "failed to receive control message: %d\n",
> r);
> - return r;
> - }
>
> - return 0;
> + return r;
> }
The callers of these functions are allocating temporary transfers buffer
for each request so this is a case where the new helpers may be of worth
if you fix up the callers as well (otherwise, you're adding redundant
memdup + memcpy for each call here).
>
> #define CH341_CLKRATE 48000000
> @@ -343,22 +334,18 @@ static int ch341_detect_quirks(struct usb_serial_port *port)
> struct usb_device *udev = port->serial->dev;
> const unsigned int size = 2;
> unsigned long quirks = 0;
> - char *buffer;
> + u8 buffer[2];
> int r;
>
> - buffer = kmalloc(size, GFP_KERNEL);
> - if (!buffer)
> - return -ENOMEM;
> -
> /*
> * A subset of CH34x devices does not support all features. The
> * prescaler is limited and there is no support for sending a RS232
> * break condition. A read failure when trying to set up the latter is
> * used to detect these devices.
> */
> - r = usb_control_msg(udev, usb_rcvctrlpipe(udev, 0), CH341_REQ_READ_REG,
> - USB_TYPE_VENDOR | USB_RECIP_DEVICE | USB_DIR_IN,
> - CH341_REG_BREAK, 0, buffer, size, DEFAULT_TIMEOUT);
> + r = usb_control_msg_recv(udev, 0, CH341_REQ_READ_REG, USB_TYPE_VENDOR |
> + USB_RECIP_DEVICE | USB_DIR_IN, CH341_REG_BREAK,
> + 0, &buffer, size, DEFAULT_TIMEOUT, GFP_KERNEL);
> if (r == -EPIPE) {
> dev_info(&port->dev, "break control not supported, using simulated break\n");
> quirks = CH341_QUIRK_LIMITED_PRESCALER | CH341_QUIRK_SIMULATE_BREAK;
> @@ -366,17 +353,13 @@ static int ch341_detect_quirks(struct usb_serial_port *port)
> goto out;
> }
>
> - if (r != size) {
> - if (r >= 0)
> - r = -EIO;
> + if (r) {
> dev_err(&port->dev, "failed to read break control: %d\n", r);
> goto out;
> }
>
> r = 0;
> out:
> - kfree(buffer);
> -
> if (quirks) {
> dev_dbg(&port->dev, "enabling quirk flags: 0x%02lx\n", quirks);
> priv->quirks |= quirks;
This is a good example of when to use the helpers. But it seems you
should remove the "r = 0" and "out" label as well, right?
Johan
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-12-04 9:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 6:46 [Linux-kernel-mentees] [PATCH 00/15] usb: serial: avoid using usb_control_msg() directly Himadri Pandya
2020-11-04 6:46 ` [Linux-kernel-mentees] [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 ` [Linux-kernel-mentees] [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 ` [Linux-kernel-mentees] [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 [this message]
2020-11-04 6:46 ` [Linux-kernel-mentees] [PATCH 04/15] usb: serial: cp210x: " Himadri Pandya
2020-12-04 9:34 ` Johan Hovold
2020-11-04 6:46 ` [Linux-kernel-mentees] [PATCH 05/15] usb: serial: cypress_m8: " Himadri Pandya
2020-12-04 9:37 ` Johan Hovold
2020-11-04 6:46 ` [Linux-kernel-mentees] [PATCH 06/15] usb: serial: f81232: " Himadri Pandya
2020-12-04 9:49 ` Johan Hovold
2020-11-04 6:46 ` [Linux-kernel-mentees] [PATCH 07/15] usb: serial: f81534: " Himadri Pandya
2020-12-04 9:55 ` Johan Hovold
2020-11-04 6:46 ` [Linux-kernel-mentees] [PATCH 08/15] usb: serial: ftdi_sio: " Himadri Pandya
2020-12-04 10:03 ` Johan Hovold
2020-11-04 6:46 ` [Linux-kernel-mentees] [PATCH 09/15] usb: serial: io_edgeport: " Himadri Pandya
2020-12-04 10:10 ` Johan Hovold
2020-11-04 6:46 ` [Linux-kernel-mentees] [PATCH 10/15] usb: serial: io_ti: " Himadri Pandya
2020-12-04 10:12 ` Johan Hovold
2020-11-04 6:46 ` [Linux-kernel-mentees] [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 ` [Linux-kernel-mentees] [PATCH 12/15] usb: serial: ipw: " Himadri Pandya
2020-12-04 10:27 ` Johan Hovold
2020-11-04 6:47 ` [Linux-kernel-mentees] [PATCH 13/15] usb: serial: iuu_phoenix: " Himadri Pandya
2020-12-04 10:28 ` Johan Hovold
2020-11-04 6:47 ` [Linux-kernel-mentees] [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 ` [Linux-kernel-mentees] [PATCH 15/15] usb: serial: kl5kusb105: " Himadri Pandya
2020-12-04 10:37 ` Johan Hovold
2020-11-06 10:43 ` [Linux-kernel-mentees] [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=X8oASVHmeoCmM5RM@localhost \
--to=johan@kernel.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).