linux-kernel - Re: [PATCH] ARM: dts: berlin: enable timer 1 for sched

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 11 Sep 2014 23:08:04 +0200
From:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
To:	Antoine Tenart <antoine.tenart@...e-electrons.com>
CC:	alexandre.belloni@...e-electrons.com,
	thomas.petazzoni@...e-electrons.com, zmxu@...vell.com,
	jszhang@...vell.com, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARM: dts: berlin: enable timer 1 for sched_clock

On 09/09/2014 04:47 PM, Antoine Tenart wrote:
> Enable timer 1 to be the source for the sched_clock, allowing to have a
> more precise value than 1/HZ.
> 
> Signed-off-by: Antoine Tenart <antoine.tenart@...e-electrons.com>

Applied to berlin/dt.

For the record, I managed to configure UTF-8, so feel free to add the
accent back to your name ;)

I applied the last patches with it already.

Sebastian

> ---
>  arch/arm/boot/dts/berlin2q.dtsi | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/arch/arm/boot/dts/berlin2q.dtsi b/arch/arm/boot/dts/berlin2q.dtsi
> index a216cb621ebc..e22b99a3a796 100644
> --- a/arch/arm/boot/dts/berlin2q.dtsi
> +++ b/arch/arm/boot/dts/berlin2q.dtsi
> @@ -247,7 +247,6 @@
>  				reg = <0x2c14 0x14>;
>  				clocks = <&chip CLKID_CFG>;
>  				clock-names = "timer";
> -				status = "disabled";
>  			};
>  
>  			timer2: timer@...8 {
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/