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
| ||
|
Date: Thu, 17 Sep 2015 14:51:44 +0100 From: Sudeep Holla <sudeep.holla@....com> To: Yingjoe Chen <yingjoe.chen@...iatek.com>, Matthias Brugger <matthias.bgg@...il.com> Cc: Sudeep Holla <sudeep.holla@....com>, Daniel Lezcano <daniel.lezcano@...aro.org>, Thomas Gleixner <tglx@...utronix.de>, Stephen Boyd <sboyd@...eaurora.org>, Michael Turquette <mturquette@...libre.com>, James Liao <jamesjj.liao@...iatek.com>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, Arnd Bergmann <arnd@...db.de>, Catalin Marinas <Catalin.Marinas@....com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Rob Herring <robh+dt@...nel.org>, "linux-mediatek@...ts.infradead.org" <linux-mediatek@...ts.infradead.org>, Sascha Hauer <kernel@...gutronix.de>, Olof Johansson <olof@...om.net>, "srv_heupstream@...iatek.com" <srv_heupstream@...iatek.com>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, Daniel Kurtz <djkurtz@...omium.org>, "linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>, Eddie Huang <eddie.huang@...iatek.com> Subject: Re: [PATCH 2/2] arm64: dts: mt8173: add timer node On 16/09/15 03:04, Yingjoe Chen wrote: > From: Daniel Kurtz <djkurtz@...omium.org> > > Add device node to enable GPT timer. This timer will be > used as sched clock source. > Interesting any known issues with or advantage over the arch timers to prefer it as sched clock source. I see even arch timers are present in DT, hence the question. Or is it just a incorrect commit log ? How does this get selected as sched clock source ? I don't see sched_clock_register in mtk_timer.c To be clear, I am not against adding this timer support, but just want to know is it preferred for sched clock source ? if yes why ? better resolution ? > Change-Id: Idc4e3f0ee80b5c36cae6f0f2328f94aafcca1253 ^ Should be dropped > Signed-off-by: Daniel Kurtz <djkurtz@...omium.org> > Signed-off-by: Eddie Huang <eddie.huang@...iatek.com> > Signed-off-by: Yingjoe Chen <yingjoe.chen@...iatek.com> > --- > arch/arm64/boot/dts/mediatek/mt8173.dtsi | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi b/arch/arm64/boot/dts/mediatek/mt8173.dtsi > index d18ee42..d763803 100644 > --- a/arch/arm64/boot/dts/mediatek/mt8173.dtsi > +++ b/arch/arm64/boot/dts/mediatek/mt8173.dtsi > @@ -238,6 +238,15 @@ > reg = <0 0x10007000 0 0x100>; > }; > > + timer: timer@...08000 { > + compatible = "mediatek,mt8173-timer", Missing documentation ? I am referring upstream and it might be in some patches already queued perhaps ? Regards, Sudeep -- 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/
Powered by blists - more mailing lists