All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: John Crispin <john@phrozen.org>
Cc: "Steven J. Hill" <Steven.Hill@imgtec.com>,
	linux-mips@linux-mips.org,
	Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>,
	ralf@linux-mips.org
Subject: Re: [PATCH v2] MIPS: GIC: Select R4K counter as fallback.
Date: Thu, 12 Sep 2013 09:38:46 +0200	[thread overview]
Message-ID: <52316F86.6010709@metafoo.de> (raw)
In-Reply-To: <52316E5D.4020100@phrozen.org>

On 09/12/2013 09:33 AM, John Crispin wrote:
> On 12/09/13 09:28, Lars-Peter Clausen wrote:
>> On 09/11/2013 09:51 PM, Steven J. Hill wrote:
>>> From: Leonid Yegoshin<Leonid.Yegoshin@imgtec.com>
>>>
>>> If CONFIG_CSRC_GIC is selected and the GIC is not found during
>>> boot, then fallback to the R4K counter gracefully.
>>
>> Is there any reason not to always register the r4k clocksource, no matter
>> whether the gic clocksource is present or not? The timekeeping core of the
>> kernel will make sure to use the best available clocksource based on the
>> clocksource's rating.
>>
>> - Lars
> 
> Hi,
> 
> in theory yes, but the r4k csrc is coded in a way that it always assumes to
> always be present and always be running.
> 

And it is not present when the GIC clocksource is present?

  reply	other threads:[~2013-09-12  7:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 19:51 [PATCH v2] MIPS: GIC: Select R4K counter as fallback Steven J. Hill
2013-09-12  6:34 ` John Crispin
2013-09-12  7:28 ` Lars-Peter Clausen
2013-09-12  7:33   ` John Crispin
2013-09-12  7:38     ` Lars-Peter Clausen [this message]
2013-09-12  8:04       ` John Crispin
2013-09-12 18:23   ` Leonid Yegoshin
2013-09-12 18:23     ` Leonid Yegoshin
2013-09-13  7:52     ` Lars-Peter Clausen

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=52316F86.6010709@metafoo.de \
    --to=lars@metafoo.de \
    --cc=Leonid.Yegoshin@imgtec.com \
    --cc=Steven.Hill@imgtec.com \
    --cc=john@phrozen.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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.