[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <mhng-3c8e382b-518c-4e32-b76e-3eebdd41034a@palmer-si-x1c4>
Date: Fri, 07 Dec 2018 09:59:33 -0800 (PST)
From: Palmer Dabbelt <palmer@...ive.com>
To: anup@...infault.org
CC: daniel.lezcano@...aro.org, tglx@...utronix.de,
aou@...s.berkeley.edu, atish.patra@....com,
Christoph Hellwig <hch@...radead.org>,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
anup@...infault.org
Subject: Re: [PATCH v2 0/2] Provide sched_clock for riscv_timer
On Tue, 04 Dec 2018 02:29:50 PST (-0800), anup@...infault.org wrote:
> This patchset extends riscv_timer to provide sched_clock using generic
> sched_clock framework.
>
> The patchset is tested on QEMU virt machine. It is based on Linux-4.20-rc5
> and can be found at riscv_sched_clock_v2 branch of:
> https://github.com/avpatel/linux.git
>
> Changes since v1:
> - Added patch to select GENERIC_SCHED_CLOCK for RISC-V
> - Kconfig RISCV_TIMER depends on GENERIC_SCHED_CLOCK
>
> Anup Patel (2):
> RISC-V: Select GENERIC_SCHED_CLOCK for clocksource drivers
> clocksource: riscv_timer: Provide sched_clock
>
> arch/riscv/Kconfig | 1 +
> drivers/clocksource/Kconfig | 2 +-
> drivers/clocksource/riscv_timer.c | 9 +++++++++
> 3 files changed, 11 insertions(+), 1 deletion(-)
I'm going to add these to my for-next, but let me know if these should go
through a clock maintainer's tree instead and I'll drop them.
Powered by blists - more mailing lists