Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

On Tue, Jul 26, 2016 at 09:11:49AM -0500, Timur Tabi wrote: > Will Deacon wrote: > >The kernel really needs to support both of those platforms :/ > > > >For the memory-mapped counter registers, the architecture says: > > > > `If the implementation supports 64-bit atomic accesses, then the > >

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

On Tue, Jul 26, 2016 at 09:11:49AM -0500, Timur Tabi wrote: > Will Deacon wrote: > >The kernel really needs to support both of those platforms :/ > > > >For the memory-mapped counter registers, the architecture says: > > > > `If the implementation supports 64-bit atomic accesses, then the > >

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

Hi all, On 27 July 2016 at 11:33, Jisheng Zhang wrote: > +1 > > On Tue, 26 Jul 2016 09:11:49 -0500 Timur Tabi wrote: > >> Will Deacon wrote: >> > The kernel really needs to support both of those platforms :/ >> > >> > For the memory-mapped counter registers, the

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

Hi all, On 27 July 2016 at 11:33, Jisheng Zhang wrote: > +1 > > On Tue, 26 Jul 2016 09:11:49 -0500 Timur Tabi wrote: > >> Will Deacon wrote: >> > The kernel really needs to support both of those platforms :/ >> > >> > For the memory-mapped counter registers, the architecture says: >> > >> >

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

+1 On Tue, 26 Jul 2016 09:11:49 -0500 Timur Tabi wrote: > Will Deacon wrote: > > The kernel really needs to support both of those platforms :/ > > > > For the memory-mapped counter registers, the architecture says: > > > >`If the implementation supports 64-bit atomic accesses, then the > >

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

+1 On Tue, 26 Jul 2016 09:11:49 -0500 Timur Tabi wrote: > Will Deacon wrote: > > The kernel really needs to support both of those platforms :/ > > > > For the memory-mapped counter registers, the architecture says: > > > >`If the implementation supports 64-bit atomic accesses, then the > >

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

Will Deacon wrote: The kernel really needs to support both of those platforms :/ For the memory-mapped counter registers, the architecture says: `If the implementation supports 64-bit atomic accesses, then the CNTV_CVAL register must be accessible as an atomic 64-bit value.' which is

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

Will Deacon wrote: The kernel really needs to support both of those platforms :/ For the memory-mapped counter registers, the architecture says: `If the implementation supports 64-bit atomic accesses, then the CNTV_CVAL register must be accessible as an atomic 64-bit value.' which is

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

Hi Russell King, On 26 July 2016 at 06:49, Russell King - ARM Linux wrote: > On Mon, Jul 25, 2016 at 05:31:45PM +0100, Will Deacon wrote: >> On Mon, Jul 25, 2016 at 11:55:49PM +0800, Fu Wei wrote: >> > On 25 July 2016 at 23:31, Will Deacon wrote: >> >

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

Hi Russell King, On 26 July 2016 at 06:49, Russell King - ARM Linux wrote: > On Mon, Jul 25, 2016 at 05:31:45PM +0100, Will Deacon wrote: >> On Mon, Jul 25, 2016 at 11:55:49PM +0800, Fu Wei wrote: >> > On 25 July 2016 at 23:31, Will Deacon wrote: >> > > On Mon, Jul 25, 2016 at 11:27:02PM +0800,

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

On Mon, Jul 25, 2016 at 05:31:45PM +0100, Will Deacon wrote: > On Mon, Jul 25, 2016 at 11:55:49PM +0800, Fu Wei wrote: > > On 25 July 2016 at 23:31, Will Deacon wrote: > > > On Mon, Jul 25, 2016 at 11:27:02PM +0800, fu@linaro.org wrote: > > >> From: Fu Wei

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

On Mon, Jul 25, 2016 at 05:31:45PM +0100, Will Deacon wrote: > On Mon, Jul 25, 2016 at 11:55:49PM +0800, Fu Wei wrote: > > On 25 July 2016 at 23:31, Will Deacon wrote: > > > On Mon, Jul 25, 2016 at 11:27:02PM +0800, fu@linaro.org wrote: > > >> From: Fu Wei > > >> > > >> This patch simplify

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

On Mon, Jul 25, 2016 at 11:55:49PM +0800, Fu Wei wrote: > On 25 July 2016 at 23:31, Will Deacon wrote: > > On Mon, Jul 25, 2016 at 11:27:02PM +0800, fu@linaro.org wrote: > >> From: Fu Wei > >> > >> This patch simplify arch_counter_get_cntvct_mem

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

On Mon, Jul 25, 2016 at 11:55:49PM +0800, Fu Wei wrote: > On 25 July 2016 at 23:31, Will Deacon wrote: > > On Mon, Jul 25, 2016 at 11:27:02PM +0800, fu@linaro.org wrote: > >> From: Fu Wei > >> > >> This patch simplify arch_counter_get_cntvct_mem function by > >> using readq to get 64-bit

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

Will Deacon wrote: > { >- u32 vct_lo, vct_hi, tmp_hi; >- >- do { >- vct_hi = readl_relaxed(arch_counter_base + CNTVCT_HI); >- vct_lo = readl_relaxed(arch_counter_base + CNTVCT_LO); >- tmp_hi = readl_relaxed(arch_counter_base + CNTVCT_HI); >- } while (vct_hi

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

Will Deacon wrote: > { >- u32 vct_lo, vct_hi, tmp_hi; >- >- do { >- vct_hi = readl_relaxed(arch_counter_base + CNTVCT_HI); >- vct_lo = readl_relaxed(arch_counter_base + CNTVCT_LO); >- tmp_hi = readl_relaxed(arch_counter_base + CNTVCT_HI); >- } while (vct_hi

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

Hi Will, On 25 July 2016 at 23:31, Will Deacon wrote: > On Mon, Jul 25, 2016 at 11:27:02PM +0800, fu@linaro.org wrote: >> From: Fu Wei >> >> This patch simplify arch_counter_get_cntvct_mem function by >> using readq to get 64-bit CNTVCT value instead

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

Hi Will, On 25 July 2016 at 23:31, Will Deacon wrote: > On Mon, Jul 25, 2016 at 11:27:02PM +0800, fu@linaro.org wrote: >> From: Fu Wei >> >> This patch simplify arch_counter_get_cntvct_mem function by >> using readq to get 64-bit CNTVCT value instead of readl_relaxed. >> >> Signed-off-by:

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

On Mon, Jul 25, 2016 at 11:27:02PM +0800, fu@linaro.org wrote: > From: Fu Wei > > This patch simplify arch_counter_get_cntvct_mem function by > using readq to get 64-bit CNTVCT value instead of readl_relaxed. > > Signed-off-by: Fu Wei > --- >

Re: [PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

On Mon, Jul 25, 2016 at 11:27:02PM +0800, fu@linaro.org wrote: > From: Fu Wei > > This patch simplify arch_counter_get_cntvct_mem function by > using readq to get 64-bit CNTVCT value instead of readl_relaxed. > > Signed-off-by: Fu Wei > --- > drivers/clocksource/arm_arch_timer.c | 10

[PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

From: Fu Wei This patch simplify arch_counter_get_cntvct_mem function by using readq to get 64-bit CNTVCT value instead of readl_relaxed. Signed-off-by: Fu Wei --- drivers/clocksource/arm_arch_timer.c | 10 +- 1 file changed, 1 insertion(+), 9

[PATCH v9 4/9] clocksource/drivers/arm_arch_timer: use readq to get 64-bit CNTVCT

From: Fu Wei This patch simplify arch_counter_get_cntvct_mem function by using readq to get 64-bit CNTVCT value instead of readl_relaxed. Signed-off-by: Fu Wei --- drivers/clocksource/arm_arch_timer.c | 10 +- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git