From: v1ron@mail.ru (Roman Volkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 RESEND 1/3] clocksource/vt8500: Use MIN_OSCR_DELTA from PXA
Date: Fri, 1 Jan 2016 02:32:08 +0300 [thread overview]
Message-ID: <20160101023208.7721e085@v1ron-s7> (raw)
In-Reply-To: <alpine.DEB.2.11.1512312331580.28591@nanos>
? Thu, 31 Dec 2015 23:33:45 +0100 (CET)
Thomas Gleixner <tglx@linutronix.de> ?????:
> Roman,
>
> On Thu, 31 Dec 2015, Roman Volkov wrote:
> > Since vt8500 and PXA timers are identical, use MIN_OSCR_DELTA from
> > PXA, which is bigger than existing value. It is required to
> > determine the minimum delay which hardware can generate.
>
> Now that brings up the obvious question:
>
> If the vt8500 and PXA timers are identical why has vt8500 it's own
> slightly different implementation and does not use the PXA timer?
Thomas,
I occasionally noticed that the PXA can be reused, when working on the
bugfix for vt8500. Another good question would be how exactly this code
can be reused. We may rework PXA driver to make it working under
vt8500, or include the C code from the vt8500 and get two slightly
different modules. You may look at our previous discussion with Alexey:
https://lkml.org/lkml/2015/12/21/437
Adding Robert and Bill to get more opinions. At this step, fixing the
vt8500 nanosleep bug is a priority.
Happy New Year,
Roman
next prev parent reply other threads:[~2015-12-31 23:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 18:02 [PATCH v2 RESEND 0/3] clocksource/vt8500: Fix hangs in small delays Roman Volkov
2015-12-31 18:02 ` [PATCH v2 RESEND 1/3] clocksource/vt8500: Use MIN_OSCR_DELTA from PXA Roman Volkov
2015-12-31 22:33 ` Thomas Gleixner
2015-12-31 23:32 ` Roman Volkov [this message]
2016-01-01 20:23 ` Robert Jarzmik
2016-01-01 9:58 ` Thomas Gleixner
2015-12-31 18:02 ` [PATCH v2 RESEND 2/3] clocksource/vt8500: Remove the 'loops' variable Roman Volkov
2015-12-31 18:02 ` [PATCH v2 RESEND 3/3] clocksource/vt8500: Add register R/W functions Roman Volkov
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=20160101023208.7721e085@v1ron-s7 \
--to=v1ron@mail.ru \
--cc=linux-arm-kernel@lists.infradead.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).