From: Michael Sweet <msweet@msweet.org>
To: Felipe Balbi <balbi@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix default q_len for usb_f_printer gadget driver
Date: Mon, 30 Nov 2020 09:17:15 -0500 [thread overview]
Message-ID: <C4FD0F03-E71F-4234-BF35-8BDFB7898900@msweet.org> (raw)
In-Reply-To: <20201030223419.3780-1-msweet@msweet.org>
[-- Attachment #1: Type: text/plain, Size: 1973 bytes --]
Hi,
I submitted this a month ago, and aside from Peter Chen's "reviewed by" response I haven't heard anything nor seen it get merged. I know you are all really busy and I don't want to be a pest - is there something else I need to do to advance this patch?
Thanks!
> On Oct 30, 2020, at 6:34 PM, Michael R Sweet <msweet@msweet.org> wrote:
>
> The usb_f_printer gadget driver uses a default q_len value of *0* which prevents
> any IO from occurring. Moreover, once the driver is instantiated it is
> impossible to change the q_len value.
>
> The following patch uses a default q_len value of 10 which matches the legacy
> g_printer gadget driver. This minimizes the possibility that you end up with a
> non-working printer gadget. It is still possible to set the q_len to a
> different value using the configfs path of the same name.
>
> Signed-off-by: Michael R Sweet <msweet@msweet.org>
> ---
> drivers/usb/gadget/function/f_printer.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/usb/gadget/function/f_printer.c b/drivers/usb/gadget/function/f_printer.c
> index 9c7ed2539ff7..4f3161005e4f 100644
> --- a/drivers/usb/gadget/function/f_printer.c
> +++ b/drivers/usb/gadget/function/f_printer.c
> @@ -50,6 +50,8 @@
> #define GET_PORT_STATUS 1
> #define SOFT_RESET 2
>
> +#define DEFAULT_Q_LEN 10 /* same as legacy g_printer gadget */
> +
> static int major, minors;
> static struct class *usb_gadget_class;
> static DEFINE_IDA(printer_ida);
> @@ -1317,6 +1319,9 @@ static struct usb_function_instance *gprinter_alloc_inst(void)
> opts->func_inst.free_func_inst = gprinter_free_inst;
> ret = &opts->func_inst;
>
> + /* Make sure q_len is initialized, otherwise the bound device can't support read/write! */
> + opts->q_len = DEFAULT_Q_LEN;
> +
> mutex_lock(&printer_ida_lock);
>
> if (ida_is_empty(&printer_ida)) {
> --
> 2.17.1
>
________________________
Michael Sweet
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 874 bytes --]
next prev parent reply other threads:[~2020-11-30 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 22:34 Michael R Sweet
2020-10-30 23:24 ` Peter Chen
2020-11-30 14:17 ` Michael Sweet [this message]
2020-12-28 17:18 Michael R Sweet
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=C4FD0F03-E71F-4234-BF35-8BDFB7898900@msweet.org \
--to=msweet@msweet.org \
--cc=balbi@kernel.org \
--cc=gregkh@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
all inboxes | Powered by JetHome®