From: Andrew Morton <akpm@osdl.org>
To: Frank Gevaerts <frank.gevaerts@fks.be>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com,
lcapitulino@mandriva.com.br
Subject: Re: [RESEND] [PATCH 2/2] ipaq.c timing parameters
Date: Mon, 19 Jun 2006 23:54:40 -0700 [thread overview]
Message-ID: <20060619235440.1be20ac3.akpm@osdl.org> (raw)
In-Reply-To: <20060619084619.GB17103@fks.be>
On Mon, 19 Jun 2006 10:46:19 +0200
Frank Gevaerts <frank.gevaerts@fks.be> wrote:
> Adds configurable waiting periods to the ipaq connection code. These are
> not needed when the pocketpc device is running normally when plugged in,
> but they need extra delays if they are physically connected while
> rebooting.
> There are two parameters :
> * initial_wait : this is the delay before the driver attemts to start the
> connection. This is needed because the pocktpc device takes much
> longer to boot if the driver starts sending control packets too soon.
> * connect_retries : this is the number of times the control urb is
> retried before finally giving up. The patch also adds a 1 second delay
> between retries.
> I'm not sure if the cases where this patch is useful are general enough
> to include this in the kernel.
>
> ..
>
> +module_param(connect_retries, int, S_IRUGO|S_IWUSR);
> +MODULE_PARM_DESC(connect_retries, "Maximum number of connect retries (100ms each)");
1000ms, methinks.
next prev parent reply other threads:[~2006-06-20 6:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 8:44 [RESEND] [PATCH 1/2] ipaq.c bugfixes Frank Gevaerts
2006-06-19 8:46 ` [RESEND] [PATCH 2/2] ipaq.c timing parameters Frank Gevaerts
2006-06-19 16:42 ` Luiz Fernando N. Capitulino
2006-06-19 17:34 ` Frank Gevaerts
2006-06-19 18:27 ` Luiz Fernando N. Capitulino
2006-06-20 6:54 ` Andrew Morton [this message]
2006-06-19 16:35 ` [RESEND] [PATCH 1/2] ipaq.c bugfixes Luiz Fernando N. Capitulino
2006-06-19 17:25 ` Frank Gevaerts
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=20060619235440.1be20ac3.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=frank.gevaerts@fks.be \
--cc=greg@kroah.com \
--cc=lcapitulino@mandriva.com.br \
--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®