From: "John W. Linville" <linville@tuxdriver.com>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Michael Wu <flamingice@sourmilk.net>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3 1/2] Add 93cx6 eeprom library
Date: Mon, 14 May 2007 14:13:23 -0400 [thread overview]
Message-ID: <20070514181323.GB6999@tuxdriver.com> (raw)
In-Reply-To: <200705141700.21900.IvDoorn@gmail.com>
On Mon, May 14, 2007 at 05:00:21PM +0200, Ivo van Doorn wrote:
> On Monday 14 May 2007 16:55, Michael Wu wrote:
> > On Monday 14 May 2007 02:49, Ivo Van Doorn wrote:
> > > For the record: I am still not happy with the removal of the udelay() from
> > > the pulse methods as they were indicated by the original Ralink code.
> > > But since I cannot test the effect on Ralink eeprom reading at this time,
> > > and I could otherwise just add it to the register_write handler if
> > > required, I am signing this off anyway.
> > >
> > The udelay is necessary to set a limit on how fast the eeprom is operated..
> > but not on all hardware, apparently. adm8211 just uses a read from the eeprom
> > register to perform the delay.
>
> Ok, then I'll update rt2x00 to perform the delay during register_write as well. :)
Actually, see the end of the thread from the previous 93cx6 patch
Michael posted on Friday. I think these delays are actually alright,
but they could use a comment. How about the patch below (applied on
top of the previous version)?
John
P.S. No need to repost any 93cx6 patches, I have them.
---
[PATCH] eeprom_93cx6: add comment explaining clocking delays
Signed-off-by: John W. Linville <linville@tuxdriver.com>
diff --git a/drivers/misc/eeprom_93cx6.c b/drivers/misc/eeprom_93cx6.c
index bfcb434..1f615ac 100644
--- a/drivers/misc/eeprom_93cx6.c
+++ b/drivers/misc/eeprom_93cx6.c
@@ -39,6 +39,8 @@ static inline void eeprom_93cx6_pulse_high(struct eeprom_93cx6 *eeprom)
{
eeprom->reg_data_clock = 1;
eeprom->register_write(eeprom);
+
+ /* honor T_ckh hold requirements from datasheet */
udelay(1);
}
@@ -46,6 +48,8 @@ static inline void eeprom_93cx6_pulse_low(struct eeprom_93cx6 *eeprom)
{
eeprom->reg_data_clock = 0;
eeprom->register_write(eeprom);
+
+ /* honor T_ckl hold requirements from datasheet */
udelay(1);
}
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-05-14 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 5:38 [PATCH v3 1/2] Add 93cx6 eeprom library Michael Wu
2007-05-14 6:49 ` Ivo Van Doorn
2007-05-14 14:55 ` Michael Wu
2007-05-14 15:00 ` Ivo van Doorn
2007-05-14 18:13 ` John W. Linville [this message]
2007-05-14 20:57 ` Ivo van Doorn
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=20070514181323.GB6999@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=flamingice@sourmilk.net \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).