From: David Miller <davem@davemloft.net>
To: robert.jarzmik@free.fr
Cc: samuel@sortiz.org, petr.cvek@tul.cz, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, arnd@arndb.de
Subject: Re: [PATCH v2 1/3] net: irda: pxaficp_ir: use sched_clock() for time management
Date: Tue, 15 Sep 2015 16:40:25 -0700 (PDT) [thread overview]
Message-ID: <20150915.164025.1543038793305792029.davem@davemloft.net> (raw)
In-Reply-To: <1442058324-9760-1-git-send-email-robert.jarzmik@free.fr>
From: Robert Jarzmik <robert.jarzmik@free.fr>
Date: Sat, 12 Sep 2015 13:45:22 +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.
>
> Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
What is the granularity of the OSCR register?
If it is not nanoseconds, then you need to adjust calculations
such as this one:
> @@ -549,7 +548,7 @@ static int pxa_irda_hard_xmit(struct sk_buff *skb, struct net_device *dev)
> skb_copy_from_linear_data(skb, si->dma_tx_buff, skb->len);
>
> if (mtt)
> - while ((unsigned)(readl_relaxed(OSCR) - si->last_oscr)/4 < mtt)
> + while ((sched_clock() - si->last_clk) / 4 < mtt)
> cpu_relax();
next prev parent reply other threads:[~2015-09-15 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 11:45 [PATCH v2 1/3] net: irda: pxaficp_ir: use sched_clock() for time management Robert Jarzmik
2015-09-12 11:45 ` [PATCH v2 2/3] net: irda: pxaficp_ir: convert to readl and writel Robert Jarzmik
2015-09-13 1:34 ` Petr Cvek
2015-09-12 11:45 ` [PATCH v2 3/3] net: irda: pxaficp_ir: dmaengine conversion Robert Jarzmik
2015-09-15 23:40 ` David Miller [this message]
2015-09-16 9:34 ` [PATCH v2 1/3] net: irda: pxaficp_ir: use sched_clock() for time management Robert Jarzmik
2015-09-17 21:51 ` David Miller
2015-09-18 16:36 ` Robert Jarzmik
2015-09-21 23:12 ` David Miller
2015-09-22 19:27 ` Robert Jarzmik
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=20150915.164025.1543038793305792029.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petr.cvek@tul.cz \
--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).