From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guido Kiener <guido@kiener-muenchen.de>
Cc: linux-usb@vger.kernel.org, guido.kiener@rohde-schwarz.com,
steve_bayless@keysight.com, dpenkler@gmail.com
Subject: [v2,08/29] usb: usbtmc: Add ioctl for generic requests on control
Date: Sat, 21 Jul 2018 08:27:36 +0200 [thread overview]
Message-ID: <20180721062736.GC24695@kroah.com> (raw)
On Wed, Jul 18, 2018 at 10:45:41AM +0200, Guido Kiener wrote:
> Add USBTMC_IOCTL_CTRL_REQUEST to send arbitrary requests on the
> control pipe. Used by specific applications of IVI Foundation,
> Inc. to implement VISA API functions: viUsbControlIn/Out.
>
> The maximum length of control request is set to 4k.
>
> Signed-off-by: Guido Kiener <guido.kiener@rohde-schwarz.com>
> Reviewed-by: Steve Bayless <steve_bayless@keysight.com>
> ---
> drivers/usb/class/usbtmc.c | 151 +++++++++++++++++++++++++++++++++++
> include/uapi/linux/usb/tmc.h | 15 ++++
> 2 files changed, 166 insertions(+)
>
> diff --git a/drivers/usb/class/usbtmc.c b/drivers/usb/class/usbtmc.c
> index d685db78b80b..846599dd0c84 100644
> --- a/drivers/usb/class/usbtmc.c
> +++ b/drivers/usb/class/usbtmc.c
> @@ -5,6 +5,7 @@
> * Copyright (C) 2007 Stefan Kopp, Gechingen, Germany
> * Copyright (C) 2008 Novell, Inc.
> * Copyright (C) 2008 Greg Kroah-Hartman <gregkh@suse.de>
> + * Copyright (C) 2018 IVI Foundation, Inc.
> */
>
> #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
> @@ -36,6 +37,9 @@
> /* Default USB timeout (in milliseconds) */
> #define USBTMC_TIMEOUT 5000
>
> +/* I/O buffer size used in generic read/write functions */
> +#define USBTMC_BUFSIZE (4096)
> +
> /*
> * Maximum number of read cycles to empty bulk in endpoint during CLEAR and
> * ABORT_BULK_IN requests. Ends the loop if (for whatever reason) a short
> @@ -126,6 +130,17 @@ struct usbtmc_file_data {
> bool term_char_enabled;
> };
>
> +#ifdef CONFIG_COMPAT
> +
> +struct compat_usbtmc_ctrlrequest {
> + struct usbtmc_request req;
> + compat_uptr_t data;
> +} __packed;
Wait, why? You are creating a new api here, why do you need a 32bit
compat layer? Just create it in a way that works for both layouts.
Just make your pointer a 64bit value and cast it to the pointer when
using it. Other ioctls do this in lots of places, making things simpler
overall. That way you don't need an ioctl compat call at all.
Please rework the code that way, don't create new apis that have to add
"old" 32bit compatibility support to them. That's just extra work you
don't need to do 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
next reply other threads:[~2018-07-21 6:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 6:27 Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-24 6:45 [v2,08/29] usb: usbtmc: Add ioctl for generic requests on control Guido Kiener
2018-07-21 11:21 Greg Kroah-Hartman
2018-07-21 11:11 Guido Kiener
2018-07-18 8:45 Guido Kiener
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=20180721062736.GC24695@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dpenkler@gmail.com \
--cc=guido.kiener@rohde-schwarz.com \
--cc=guido@kiener-muenchen.de \
--cc=linux-usb@vger.kernel.org \
--cc=steve_bayless@keysight.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).