From: Simon Arlott <simon@fire.lp0.eu>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cxacru: Use a bulk URB to access the command endpoint
Date: Tue, 31 Aug 2010 23:06:24 +0100 [thread overview]
Message-ID: <4C7D7CE0.4080308@simon.arlott.org.uk> (raw)
In-Reply-To: <4C7C27B5.5080904@simon.arlott.org.uk>
Please drop this patch, I'll make a version that detects which type of
endpoint it is and uses an interrupt or bulk URB as appropriate. Some
devices which may/may not be compatible appear to have interrupt
command endpoints as referenced in the original comment.
On 30/08/10 22:50, Simon Arlott wrote:
> The command endpoint is a bulk endpoint, but interrupt transfers
> are used to access it when checking status, load firmware or alter
> the configuration.
>
> This causes an error if CONFIG_USB_DEBUG is enabled after commit
> f661c6f8c67bd55e93348f160d590ff9edf08904, which checks for this
> mismatch.
>
> Signed-off-by: Simon Arlott <simon@fire.lp0.eu>
> ---
> drivers/usb/atm/cxacru.c | 14 +++++++-------
> 1 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/usb/atm/cxacru.c b/drivers/usb/atm/cxacru.c
> index 593fc5e..3b45f57 100644
> --- a/drivers/usb/atm/cxacru.c
> +++ b/drivers/usb/atm/cxacru.c
> @@ -49,7 +49,7 @@
>
> static const char cxacru_driver_name[] = "cxacru";
>
> -#define CXACRU_EP_CMD 0x01 /* Bulk/interrupt in/out */
> +#define CXACRU_EP_CMD 0x01 /* Bulk in/out */
> #define CXACRU_EP_DATA 0x02 /* Bulk in/out */
>
> #define CMD_PACKET_SIZE 64 /* Should be maxpacket(ep)? */
> @@ -1171,15 +1171,15 @@ static int cxacru_bind(struct usbatm_data *usbatm_instance,
> goto fail;
> }
>
> - usb_fill_int_urb(instance->rcv_urb,
> - usb_dev, usb_rcvintpipe(usb_dev, CXACRU_EP_CMD),
> + usb_fill_bulk_urb(instance->rcv_urb,
> + usb_dev, usb_rcvbulkpipe(usb_dev, CXACRU_EP_CMD),
> instance->rcv_buf, PAGE_SIZE,
> - cxacru_blocking_completion, &instance->rcv_done, 1);
> + cxacru_blocking_completion, &instance->rcv_done);
>
> - usb_fill_int_urb(instance->snd_urb,
> - usb_dev, usb_sndintpipe(usb_dev, CXACRU_EP_CMD),
> + usb_fill_bulk_urb(instance->snd_urb,
> + usb_dev, usb_sndbulkpipe(usb_dev, CXACRU_EP_CMD),
> instance->snd_buf, PAGE_SIZE,
> - cxacru_blocking_completion, &instance->snd_done, 4);
> + cxacru_blocking_completion, &instance->snd_done);
>
> mutex_init(&instance->cm_serialize);
>
--
Simon Arlott
prev parent reply other threads:[~2010-08-31 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 21:50 Simon Arlott
2010-08-31 22:06 ` Simon Arlott [this message]
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=4C7D7CE0.4080308@simon.arlott.org.uk \
--to=simon@fire.lp0.eu \
--cc=greg@kroah.com \
--cc=linux-kernel@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®