From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Ivo Manca <pinkel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Hans de Goede <j.w.r.degoede-fbo2DhPpy/Q@public.gmane.org>,
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [PATCH 01/03] i2c-i801: Add basic interrupt support
Date: Wed, 13 Aug 2008 22:38:40 +0200 [thread overview]
Message-ID: <20080813223840.42ad6fb3@hyperion.delvare> (raw)
In-Reply-To: <48A33342.1050105-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Wed, 13 Aug 2008 21:17:22 +0200, Ivo Manca wrote:
> Hey Jean,
> > Ideally this define would replace MAX_TIMEOUT (in a separate patch) so
> > that both
> > the poll-based and the interrupt-driven paths have the same timeout
> > value. Right now,
> > the timeout handling of the poll-based path is rather ugly (the actual
> > timeout depends on
> > the value of HZ.)
>
> Hm, seems like a very sensible thing to do. However, I have no idea how
> to implement that, since you don't really know how long msleep slept, or
> not? I sadly don't really have time to look into this right now, sorry.
The trick is to not rely on the duration of the msleep(). As you
rightly said, we have no clue how long it slept. Instead, we remember
the initial value of jiffies, and check after each iteration whether
the timeout has been exceeded or not. Something like:
unsigned long start = jiffies, now;
while (!time_after(now, jiffies + timeout)
&& !<other condition>) {
msleep(1);
<do something>
}
But if you don't have the time, this can be done later, no worry. It
doesn't belong to your patch anyway.
> (...)
> I'll send you an updated patch later this evening. I don't know anything
> about config files though, so that'll have to wait a bit... The module
> parameter will be added though.
The Kconfig language is pretty easy. But don't worry about it if you
don't have the time to look into it: I'll add a patch on top of yours
implementing my idea, no problem.
Thanks,
--
Jean Delvare
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
prev parent reply other threads:[~2008-08-13 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 16:56 [PATCH 01/03] i2c-i801: Add basic interrupt support Ivo Manca
[not found] ` <488762C8.6090105-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-08-12 8:15 ` Jean Delvare
[not found] ` <20080812101545.600ca850-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-08-13 19:17 ` Ivo Manca
[not found] ` <48A33342.1050105-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-08-13 19:59 ` Ivo Manca
2008-08-13 20:38 ` Jean Delvare [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=20080813223840.42ad6fb3@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=j.w.r.degoede-fbo2DhPpy/Q@public.gmane.org \
--cc=pinkel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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