From: Mitchel Humpherys <mitchelh-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Matt Wagantall <mattw-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v4 1/2] iopoll: Introduce memory-mapped IO polling macros
Date: Thu, 09 Oct 2014 15:45:05 -0700 [thread overview]
Message-ID: <vnkwppe07thq.fsf@mitchelh-linux.qualcomm.com> (raw)
In-Reply-To: <vnkwoatngwmo.fsf-Yf+dfxj6toJBVvN7MMdr1KRtKmQZhJ7pQQ4Iyu8u01E@public.gmane.org> (Mitchel Humpherys's message of "Tue, 07 Oct 2014 18:47:59 -0700")
On Tue, Oct 07 2014 at 06:47:59 PM, Mitchel Humpherys <mitchelh-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> wrote:
>>> +#define readl_poll_timeout_atomic(addr, val, cond, max_reads, time_between_us) \
>>> +({ \
>>> + int count; \
>>> + for (count = (max_reads); count > 0; count--) { \
>>> + (val) = readl(addr); \
>>> + if (cond) \
>>> + break; \
>>> + udelay(time_between_us); \
>>> + } \
>>> + (cond) ? 0 : -ETIMEDOUT; \
>>> +})
>>
>> udelay has a large variability, I think it would be better to also use
>> ktime_compare here and make the interface the same as the other one.
>> You might want to add a warning if someone tries to pass more than a few
>> microseconds as the timeout.
>
> Sounds good, will update in v5.
Except I'll probably hold off on adding a warning about udelay since
udelay already includes a "warning" (a compile error, actually) when
exceedingly large delays are requested.
-Mitch
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: mitchelh@codeaurora.org (Mitchel Humpherys)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/2] iopoll: Introduce memory-mapped IO polling macros
Date: Thu, 09 Oct 2014 15:45:05 -0700 [thread overview]
Message-ID: <vnkwppe07thq.fsf@mitchelh-linux.qualcomm.com> (raw)
In-Reply-To: <vnkwoatngwmo.fsf@mitchelh-linux.qualcomm.com> (Mitchel Humpherys's message of "Tue, 07 Oct 2014 18:47:59 -0700")
On Tue, Oct 07 2014 at 06:47:59 PM, Mitchel Humpherys <mitchelh@codeaurora.org> wrote:
>>> +#define readl_poll_timeout_atomic(addr, val, cond, max_reads, time_between_us) \
>>> +({ \
>>> + int count; \
>>> + for (count = (max_reads); count > 0; count--) { \
>>> + (val) = readl(addr); \
>>> + if (cond) \
>>> + break; \
>>> + udelay(time_between_us); \
>>> + } \
>>> + (cond) ? 0 : -ETIMEDOUT; \
>>> +})
>>
>> udelay has a large variability, I think it would be better to also use
>> ktime_compare here and make the interface the same as the other one.
>> You might want to add a warning if someone tries to pass more than a few
>> microseconds as the timeout.
>
> Sounds good, will update in v5.
Except I'll probably hold off on adding a warning about udelay since
udelay already includes a "warning" (a compile error, actually) when
exceedingly large delays are requested.
-Mitch
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2014-10-09 22:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 1:28 [PATCH v4 0/2] iommu/arm-smmu: hard iova_to_phys Mitchel Humpherys
2014-10-01 1:28 ` Mitchel Humpherys
[not found] ` <1412126893-15796-1-git-send-email-mitchelh-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-10-01 1:28 ` [PATCH v4 1/2] iopoll: Introduce memory-mapped IO polling macros Mitchel Humpherys
2014-10-01 1:28 ` Mitchel Humpherys
[not found] ` <1412126893-15796-2-git-send-email-mitchelh-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-10-01 8:25 ` Arnd Bergmann
2014-10-01 8:25 ` Arnd Bergmann
2014-10-08 1:47 ` Mitchel Humpherys
2014-10-08 1:47 ` Mitchel Humpherys
[not found] ` <vnkwoatngwmo.fsf-Yf+dfxj6toJBVvN7MMdr1KRtKmQZhJ7pQQ4Iyu8u01E@public.gmane.org>
2014-10-08 13:40 ` Arnd Bergmann
2014-10-08 13:40 ` Arnd Bergmann
2014-10-10 19:44 ` Mitchel Humpherys
2014-10-10 19:44 ` Mitchel Humpherys
[not found] ` <vnkwoatjn1zm.fsf-Yf+dfxj6toJBVvN7MMdr1KRtKmQZhJ7pQQ4Iyu8u01E@public.gmane.org>
2014-10-10 19:50 ` Arnd Bergmann
2014-10-10 19:50 ` Arnd Bergmann
2014-10-10 20:24 ` Mitchel Humpherys
2014-10-10 20:24 ` Mitchel Humpherys
2014-10-09 22:45 ` Mitchel Humpherys [this message]
2014-10-09 22:45 ` Mitchel Humpherys
2014-10-01 1:28 ` [PATCH v4 2/2] iommu/arm-smmu: add support for iova_to_phys through ATS1PR Mitchel Humpherys
2014-10-01 1:28 ` Mitchel Humpherys
[not found] ` <1412126893-15796-3-git-send-email-mitchelh-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-10-01 8:27 ` Arnd Bergmann
2014-10-01 8:27 ` Arnd Bergmann
2014-10-01 19:52 ` Mitchel Humpherys
2014-10-01 19:52 ` Mitchel Humpherys
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=vnkwppe07thq.fsf@mitchelh-linux.qualcomm.com \
--to=mitchelh-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mattw-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.