From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Alexey Brodkin <alexey.brodkin@synopsys.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"vineet.gupta1@synopsys.com" <vineet.gupta1@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH v2] clocksource/drivers/arc_timer: Utilize generic sched_clock
Date: Mon, 19 Nov 2018 10:58:39 +0100 [thread overview]
Message-ID: <6bb98a9c-899e-ee9c-d630-da07382c1c16@linaro.org> (raw)
In-Reply-To: <e31a11c42c21353963bd75c88493e8158316d469.camel@synopsys.com>
Hi Alexey,
On 19/11/2018 10:55, Alexey Brodkin wrote:
> Hi Daniel,
[ ... ]
>>> In that case do I understand correctly that we may enable GENERIC_SCHED_CLOCK
>>> for ARC even before proposed change for arc_timer.c gets merged - i.e. with no
>>> special GENERIC_SCHED_CLOCK driver we'll safely fall-back to jiffie-based
>>> sched clock which we anyways use now when GENERIC_SCHED_CLOCK is disabled, right?
>>
>> The ARC's Kconfig part does not apply on tip/timers/core.
>
> May I have a reference to that tree so I may check what gets in the way there
> and then I'll just move "select GENERIC_SCHED_CLOCK" a bit below so there're no
> clashes any longer.
sure, here it is:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=timers/core
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2018-11-19 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 11:30 Alexey Brodkin
2018-10-23 22:33 ` Vineet Gupta
2018-11-05 14:39 ` Daniel Lezcano
2018-11-18 2:17 ` Daniel Lezcano
2018-11-19 9:31 ` Alexey Brodkin
2018-11-19 9:43 ` Daniel Lezcano
2018-11-19 9:55 ` Alexey Brodkin
2018-11-19 9:58 ` Daniel Lezcano [this message]
2018-11-19 11:30 ` Alexey Brodkin
2018-11-05 14:48 ` Daniel Lezcano
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=6bb98a9c-899e-ee9c-d630-da07382c1c16@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=alexey.brodkin@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=tglx@linutronix.de \
--cc=vineet.gupta1@synopsys.com \
/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
all inboxes | Powered by JetHome®