linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: John Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] eeprom_93cx6: Add comment for 1us delay after pulse
Date: Mon, 14 May 2007 22:49:10 -0400	[thread overview]
Message-ID: <46491FA6.9050403@garzik.org> (raw)
In-Reply-To: <200705142306.01172.IvDoorn@gmail.com>

Ivo van Doorn wrote:
> This will add a comment for the 1us delay which is taken
> after the pulse has been switched. The 1us delay is based
> on the specifications so that should be made clear.
> 
> Signed-off-by: Ivo van Doorn <IvDoorn@gmail.com>
> 
> ---
> 
> diff --git a/drivers/misc/eeprom_93cx6.c b/drivers/misc/eeprom_93cx6.c
> index a948ddc..8c8b43f 100644
> --- a/drivers/misc/eeprom_93cx6.c
> +++ b/drivers/misc/eeprom_93cx6.c
> @@ -39,6 +39,12 @@ static inline void eeprom_93cx6_pulse_high(struct eeprom_93cx6 *eeprom)
>  {
>  	eeprom->reg_data_clock = 1;
>  	eeprom->register_write(eeprom);
> +
> +	/*
> +	 * Add a short delay for the pulse to work.
> +	 * According to the specifications the minimal time
> +	 * should be 450ns so a 1us delay is sufficient.
> +	 */
>  	udelay(1);
>  }
>  
> @@ -46,6 +52,12 @@ static inline void eeprom_93cx6_pulse_low(struct eeprom_93cx6 *eeprom)
>  {
>  	eeprom->reg_data_clock = 0;
>  	eeprom->register_write(eeprom);
> +
> +	/*
> +	 * Add a short delay for the pulse to work.
> +	 * According to the specifications the minimal time
> +	 * should be 450ns so a 1us delay is sufficient.
> +	 */
>  	udelay(1);

why not ndelay(450)?

	Jeff




      reply	other threads:[~2007-05-15  2:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14 21:06 [PATCH] eeprom_93cx6: Add comment for 1us delay after pulse Ivo van Doorn
2007-05-15  2:49 ` Jeff Garzik [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=46491FA6.9050403@garzik.org \
    --to=jeff@garzik.org \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).