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: Wed, 19 Jun 2013 09:16:12 +0200 From: Lukasz Majewski <l.majewski@...sung.com> To: "Rafael J. Wysocki" <rjw@...k.pl>, Viresh Kumar <viresh.kumar@...aro.org> Cc: Lukasz Majewski <l.majewski@...sung.com>, "cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>, Linux PM list <linux-pm@...r.kernel.org>, Vincent Guittot <vincent.guittot@...aro.org>, Jonghwa Lee <jonghwa3.lee@...sung.com>, Myungjoo Ham <myungjoo.ham@...sung.com>, linux-kernel <linux-kernel@...r.kernel.org>, Lukasz Majewski <l.majewski@...ess.pl>, Andre Przywara <andre.przywara@...aro.org>, Daniel Lezcano <daniel.lezcano@...aro.org>, Kukjin Kim <kgene.kim@...sung.com>, Amit Daniel Kachhap <amit.daniel@...sung.com> Subject: Re: [PATCH v3 1/3] cpufreq: Add boost frequency support in core On Tue, 18 Jun 2013 15:44:56 +0200, Lukasz Majewski wrote: Dear Viesh, Rafael, > > > > I'd recommend you both to read Documentation/cpu-freq/boost.txt > > now. :-) > > > According to the documentation: > "Reading the file is always supported, even if the processor does not > support boosting. In this case the file will be read-only and always > reads as "0"" > > Hmm, in the proposed patch set, the "boost" attribute is only exported > when cpufreq driver sets boost_supported flag. I would like to clarify the above issue. When I've discussed with Viresh previous version of this patch, we have agreed, that "boost" sysfs attribute [*]: /sys/devices/system/cpu/cpufreq/boost would be only visible when boost_supported flag is set at cpufreq driver. When acpi-cpufreq driver doesn't support boost, the attribute [*] won't be exported at all. This contradicts the documentation and legacy acpi-cpufreq behaviour. Since I'm affraid to break API (with all its consequences :-) ), I would like to be sure that this is OK, and thereof I'm allowed to rewrite documentation accordingly. I simply need explicit permission from both maintainers :-). -- Best regards, Lukasz Majewski Samsung R&D Institute Poland (SRPOL) | Linux Platform Group -- 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