From: Greg KH <greg@kroah.com>
To: Martin Bammer <mrbm74@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: usb-storage: Wait less time for settling when a memory device is connected
Date: Fri, 6 Mar 2009 09:49:13 -0800 [thread overview]
Message-ID: <20090306174913.GB3099@kroah.com> (raw)
In-Reply-To: <1236335647.16732.12.camel@localhost>
On Fri, Mar 06, 2009 at 11:34:07AM +0100, Martin Bammer wrote:
> Hi,
First off, usb issues/patches should be sent to the
linux-usb@vger.kernel.org list so they don't get ignored.
> I was wondering why the usb-storage driver waits for my usb-stick and my
> sdhc-card 5s before scanning. IMHO this is only needed for HDs. I've
> created a patch for the driver which shortens the timeout to 1s when a
> memory device is detected.
> But I'm not shure if the detection code is right for all devices. This
> maybe has to be tested and discussed.
> I've tested it with a usb-stick, a sdhc-card and a usb-harddrive.
> This patch is created for kernel 2.6.27.18.
>
> Please CC me for answers to this thread.
>
> --- a/drivers/usb/storage/usb.c 2009-03-03 23:33:37.000000000 +0100
> +++ b/drivers/usb/storage/usb.c 2009-03-03 23:32:44.000000000 +0100
> @@ -913,10 +913,16 @@ static int usb_stor_scan_thread(void * _
>
> set_freezable();
>
> + /* Shorten delay time for memory sticks/cards */
> + if ((1 == us->pusb_dev->descriptor.iManufacturer)
> + && (2 == us->pusb_dev->descriptor.iProduct)
> + && (3 == us->pusb_dev->descriptor.iSerialNumber)
> + && (delay_use > 0)) delay_use = 1;
Please always run your patches through scripts/checkpatch.pl first.
Why are you testing for the manufacturer and product here?
And what's wrong with just changing the module parameter for delay_use,
that is what it is there for. No kernel patch should be needed.
thanks,
greg k-h
prev parent reply other threads:[~2009-03-06 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 10:34 usb-storage: Wait less time for settling when a memory device is connected Martin Bammer
2009-03-06 17:49 ` Greg KH [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=20090306174913.GB3099@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrbm74@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.