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: Fri, 22 May 2015 08:16:16 -0700 From: Guenter Roeck <linux@...ck-us.net> To: Timur Tabi <timur@...eaurora.org> Cc: fu.wei@...aro.org, Suravee.Suthikulpanit@....com, linaro-acpi@...ts.linaro.org, linux-watchdog@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org, tekkamanninja@...il.com, graeme.gregory@...aro.org, al.stone@...aro.org, hanjun.guo@...aro.org, ashwin.chaugule@...aro.org, arnd@...db.de, vgandhi@...eaurora.org, wim@...ana.be, jcm@...hat.com, leo.duran@....com, corbet@....net, mark.rutland@....com Subject: Re: [PATCH v2 1/7] clocksource: export "arch_timer_get_rate" for the other drivers On Fri, May 22, 2015 at 09:09:10AM -0500, Timur Tabi wrote: > fu.wei@...aro.org wrote: > >Some devices get clock from system counter, like SBSA watchdog > >driver. They may need to get system counter rate. > > We don't need this patch. The watchdog driver can use > arch_timer_get_cntfrq() instead of arch_timer_get_rate(). There's nothing > wrong with arch_timer_get_cntfrq() since the SBSA driver is intended only > for ARM64 server systems, and arch_timer_get_cntfrq() is always defined for > such systems. > I agree, since the SBSA driver also uses arch_counter_get_cntvct() which is declared in the same include file as arch_timer_get_cntfrq(). The additional dependency does not provide any value, unless architecture implementation dependencies can be removed entirely, which does not seem to be the case. Doo bad that SBSA is not hardware independent enough to provide all the information needed to implement such a driver :-(. Guenter -- 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