From: Anant Thazhemadam <anant.thazhemadam@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Anant Thazhemadam <anant.thazhemadam@gmail.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: [PATCH 00/15] drivers: usb: misc: update to use usb_control_msg_{send|recv}()
Date: Sun, 29 Nov 2020 21:35:57 +0530 [thread overview]
Message-ID: <20201129160612.1908074-1-anant.thazhemadam@gmail.com> (raw)
The new usb_control_msg_{send|recv}() API provides an improved way of
using usb_control_msg(). Using this, short reads/writes are considered
as errors, data can be used off the stack, and the need for the calling
function to create a raw usb pipe is eliminated.
This patch series aims to update existing instances of usb_control_msg()
in drivers/usb/misc to usb_control_msg_{send|recv}() appropriately, and
also update the return value checking mechanisms in place (if any), as
necessary so nothing breaks.
I was however unable to update one instance of usb_control_msg() in
drivers/usb/misc/apple-mfi-fastcharge.c.
The return value checking mechanism present here, is as follows.
if (retval) {
dev_dbg(&mfi->udev->dev, "retval = %d\n", retval);
return retval;
}
mfi->charge_type = val->intval;
return 0;
This implies that mfi->charge_type = val->intval only when number of
bytes transferred = 0, and the return value is directly returned
otherwise. Since the new API doesn't return the number of bytes
transferred, I wasn't quite sure how this instance could be updated.
In case this check is logically incorrect, a patch with a fix
can be sent in as well.
Anant Thazhemadam (15):
usb: misc: appledisplay: update to use the
usb_control_msg_{send|recv}() API
usb: misc: cypress_cy7c63: update to use usb_control_msg_recv()
usb: misc: cytherm: update to use usb_control_msg_recv()
usb: misc: ehset: update to use the usb_control_msg_{send|recv}() API
usb: misc: emi26: update to use usb_control_msg_send()
usb: misc: emi62: update to use usb_control_msg_send()
usb: misc: ezusb: update to use usb_control_msg_send()
usb: misc: idmouse: update to use usb_control_msg_send()
usb: misc: iowarrior: update to use the usb_control_msg_{send|recv}()
API
usb: misc: isight_firmware: update to use usb_control_msg_send()
usb: misc: ldusb: update to use usb_control_msg_send()
usb: misc: lvstest: update to use the usb_control_msg_{send|recv}()
API
usb: misc: trancevibrator: update to use usb_control_msg_send()
usb: misc: usbsevseg: update to use usb_control_msg_send()
usb: misc: usbtest: update to use the usb_control_msg_{send|recv}()
API
drivers/usb/misc/appledisplay.c | 46 ++++++++------------
drivers/usb/misc/cypress_cy7c63.c | 10 ++---
drivers/usb/misc/cytherm.c | 42 +++++++++---------
drivers/usb/misc/ehset.c | 70 +++++++++++++-----------------
drivers/usb/misc/emi26.c | 14 +-----
drivers/usb/misc/emi62.c | 14 +-----
drivers/usb/misc/ezusb.c | 16 +------
drivers/usb/misc/idmouse.c | 5 ++-
drivers/usb/misc/iowarrior.c | 34 +++++++--------
drivers/usb/misc/isight_firmware.c | 22 +++++-----
drivers/usb/misc/ldusb.c | 8 ++--
drivers/usb/misc/lvstest.c | 30 ++++++-------
drivers/usb/misc/trancevibrator.c | 6 +--
drivers/usb/misc/usbsevseg.c | 52 +++++++---------------
drivers/usb/misc/usbtest.c | 63 +++++++++++++--------------
15 files changed, 180 insertions(+), 252 deletions(-)
--
2.25.1
next reply other threads:[~2020-11-29 16:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 16:05 Anant Thazhemadam [this message]
2020-11-29 16:05 ` [PATCH 01/15] usb: misc: appledisplay: update to use the usb_control_msg_{send|recv}() API Anant Thazhemadam
2020-11-29 16:05 ` [PATCH 02/15] usb: misc: cypress_cy7c63: update to use usb_control_msg_recv() Anant Thazhemadam
2020-11-29 16:06 ` [PATCH 03/15] usb: misc: cytherm: " Anant Thazhemadam
2020-11-29 16:16 ` Greg Kroah-Hartman
2020-11-29 16:38 ` Anant Thazhemadam
2020-11-29 16:06 ` [PATCH 04/15] usb: misc: ehset: update to use the usb_control_msg_{send|recv}() API Anant Thazhemadam
2020-12-07 2:25 ` Peter Chen
2020-11-29 16:06 ` [PATCH 05/15] usb: misc: emi26: update to use usb_control_msg_send() Anant Thazhemadam
2020-11-29 16:06 ` [PATCH 06/15] usb: misc: emi62: " Anant Thazhemadam
2020-11-29 16:06 ` [PATCH 07/15] usb: misc: ezusb: " Anant Thazhemadam
2020-11-29 16:06 ` [PATCH 08/15] usb: misc: idmouse: " Anant Thazhemadam
2020-11-29 16:06 ` [PATCH 09/15] usb: misc: iowarrior: update to use the usb_control_msg_{send|recv}() API Anant Thazhemadam
2020-11-29 16:06 ` [PATCH 10/15] usb: misc: isight_firmware: update to use usb_control_msg_send() Anant Thazhemadam
2020-11-29 16:06 ` [PATCH 11/15] usb: misc: ldusb: " Anant Thazhemadam
2020-11-29 16:06 ` [PATCH 12/15] usb: misc: lvstest: update to use the usb_control_msg_{send|recv}() API Anant Thazhemadam
2020-11-29 16:06 ` [PATCH 13/15] usb: misc: trancevibrator: update to use usb_control_msg_send() Anant Thazhemadam
2020-11-29 16:06 ` [PATCH 14/15] usb: misc: usbsevseg: " Anant Thazhemadam
2020-11-29 16:06 ` [PATCH 15/15] usb: misc: usbtest: update to use the usb_control_msg_{send|recv}() API Anant Thazhemadam
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=20201129160612.1908074-1-anant.thazhemadam@gmail.com \
--to=anant.thazhemadam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.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).