From: Kylene Jo Hall <kjhall@us.ibm.com>
To: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
akpm@osdl.org,
TPM Device Driver List <tpmdd-devel@lists.sourceforge.net>
Subject: Re: [PATCH 7/7] tpm: Driver for next generation TPM chips
Date: Wed, 12 Apr 2006 12:29:17 -0500 [thread overview]
Message-ID: <1144862957.12054.59.camel@localhost.localdomain> (raw)
In-Reply-To: <20060411230505.GB21210@us.ibm.com>
On Tue, 2006-04-11 at 16:05 -0700, Nishanth Aravamudan wrote:
> return l;
> > +
> > + } else {
> > + /* wait for burstcount */
> > + stop = jiffies + (HZ * chip->vendor.timeout_a / 1000);
> > + do {
> > + if (check_locality(chip, l) >= 0)
> > + return l;
> > + msleep(TPM_TIMEOUT);
> > + }
> > + while (time_before(jiffies, stop));
> > + }
>
> This looks like it could take the msecs_to_jiffies() conversion as well.
> Might as well cache it before the if/else, as both clauses use it?
> Really, it is just wait_event*() without the wait-queue. Well, this is
> at least one more consumer potentially of the poll_event*() API I had
> written a while back, I'll dust it off again if I have the time.
>
> <snip>
>
> > +static int get_burstcount(struct tpm_chip *chip)
> > +{
> > + unsigned long stop;
> > + int burstcnt;
> > +
> > + /* wait for burstcount */
> > + /* which timeout value, spec has 2 answers (c & d) */
> > + stop = jiffies + (HZ * chip->vendor.timeout_d / 1000);
>
> msecs_to_jiffies().
>
Since the timeout and duration values are always used in jiffies I think
I'll just convert them to those values when I store them in the chip
struct to cut way down on the number of conversions all together. Sound
reasonable?
Thanks,
Kylie
next prev parent reply other threads:[~2006-04-12 17:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 14:37 Kylene Jo Hall
2006-04-10 22:03 ` Andrew Morton
2006-04-11 20:15 ` [PATCH] tpm: update to use wait_event calls Kylene Jo Hall
2006-04-11 20:31 ` Nish Aravamudan
2006-04-11 22:32 ` [PATCH] tpm: use wait_event return code and msecs_to_jiffies Kylene Jo Hall
2006-04-11 20:40 ` [PATCH] tpm: update to use wait_event calls Ingo Oeser
2006-04-11 23:05 ` [PATCH 7/7] tpm: Driver for next generation TPM chips Nishanth Aravamudan
2006-04-12 17:29 ` Kylene Jo Hall [this message]
2006-04-12 17:32 ` Nishanth Aravamudan
2006-04-12 21:48 ` [PATCH] tpm: msecs_to_jiffies cleanups Kylene Jo Hall
-- strict thread matches above, loose matches on Subject: below --
2006-04-05 19:48 [PATCH 7/7] tpm: Driver for next generation TPM chips Kylene Jo Hall
2006-04-03 16:42 Kylene Jo Hall
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=1144862957.12054.59.camel@localhost.localdomain \
--to=kjhall@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nacc@us.ibm.com \
--cc=tpmdd-devel@lists.sourceforge.net \
/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
Powered by JetHome