From: David Miller <davem@davemloft.net>
To: robert.jarzmik@free.fr
Cc: samuel@sortiz.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] net: irda: pxaficp_ir: use sched_clock() for time management
Date: Mon, 28 Sep 2015 22:33:10 -0700 (PDT) [thread overview]
Message-ID: <20150928.223310.709463014669733152.davem@davemloft.net> (raw)
In-Reply-To: <1443293360-16377-1-git-send-email-robert.jarzmik@free.fr>
From: Robert Jarzmik <robert.jarzmik@free.fr>
Date: Sat, 26 Sep 2015 20:49:18 +0200
> Instead of using directly the OS timer through direct register access,
> use the standard sched_clock(), which will end up in OSCR reading
> anyway.
>
> This is a first step for direct access register removal and machine
> specific code removal from this driver.
>
> This commit changes the behavior, as previously the minimum turnaround
> time was counted in 76ns steps, while with this patch it is counted in
> microsecond steps. The strictly equal formula would have been :
> while ((sched_clock() - si->last_clk) * 76 < mtt)
>
> Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
> ---
> Since v2: fixed clock calculation as pointed out by David
Applied to net-next.
prev parent reply other threads:[~2015-09-29 5:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 18:49 [PATCH v3 1/3] net: irda: pxaficp_ir: use sched_clock() for time management Robert Jarzmik
2015-09-26 18:49 ` [PATCH v3 2/3] net: irda: pxaficp_ir: convert to readl and writel Robert Jarzmik
2015-09-29 5:33 ` David Miller
2015-09-26 18:49 ` [PATCH v3 3/3] net: irda: pxaficp_ir: dmaengine conversion Robert Jarzmik
2015-09-29 5:33 ` David Miller
2015-09-29 5:33 ` David Miller [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=20150928.223310.709463014669733152.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
--cc=samuel@sortiz.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).