Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1209696
| From | Antoine Tenart <antoine.tenart@free-electrons.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2 0/6] ARM: berlin: add cpufreq support |
| Date | 2015-08-19 10:20 +0200 |
| Message-ID | <pZ6Lf-eM-5@gated-at.bofh.it> (permalink) |
| References | <pYNyW-55G-7@gated-at.bofh.it> <pYOEG-6Gh-9@gated-at.bofh.it> <pYQdr-BV-1@gated-at.bofh.it> <pYQwO-YL-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Aug 18, 2015 at 08:29:25PM +0530, Viresh Kumar wrote: > On 18-08-15, 16:39, Antoine Tenart wrote: > > However, it seems the OPP-v2 table takes precedence over the old one. > > When a default OPP-v2 table is supplied in the device tree, if the > > bootloader supplies an OPP table the old way it won't be taken into > > account. > > > > So if I understood correctly, this won't work here for the BG2Q. > > Didn't understood it completely. Are you saying that your dtb will > have two operating-points tables ? Yes. If the device tree has an OPP-v2 table and the bootloader modify it to add an old OPP table at boot, the one added by the bootloader won't be taken into account by the kernel. > The deal is that for any device, parsing of opp-v2 will be attempted > first. If its not available, then opp-v1 will be tried. But this is > per-device. So, one device can have opp-v2 tables and other one can do > v1 type. Sure. OPP-v2 tables can be used for devices having an up-to-date bootloader or if the bootloader do not modify the device tree at boot time to add an (old) OPP table. Antoine -- Antoine Ténart, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH v2 0/6] ARM: berlin: add cpufreq support Antoine Tenart <antoine.tenart@free-electrons.com> - 2015-08-18 13:50 +0200
[PATCH v2 6/6] ARM: berlin: register cpufreq-dt Antoine Tenart <antoine.tenart@free-electrons.com> - 2015-08-18 13:50 +0200
[PATCH v2 2/6] clk: berlin: add cpuclk Antoine Tenart <antoine.tenart@free-electrons.com> - 2015-08-18 13:50 +0200
[PATCH v2 5/6] ARM: berlin: dts: add the cpufreq-dt bindings on the BG2CD Antoine Tenart <antoine.tenart@free-electrons.com> - 2015-08-18 13:50 +0200
[PATCH v2 4/6] ARM: berlin: dts: add the cpufreq-dt bindings on the BG2 Antoine Tenart <antoine.tenart@free-electrons.com> - 2015-08-18 13:50 +0200
Re: [PATCH v2 0/6] ARM: berlin: add cpufreq support Viresh Kumar <viresh.kumar@linaro.org> - 2015-08-18 15:00 +0200
Re: [PATCH v2 0/6] ARM: berlin: add cpufreq support Antoine Tenart <antoine.tenart@free-electrons.com> - 2015-08-18 16:40 +0200
Re: [PATCH v2 0/6] ARM: berlin: add cpufreq support Viresh Kumar <viresh.kumar@linaro.org> - 2015-08-18 17:00 +0200
Re: [PATCH v2 0/6] ARM: berlin: add cpufreq support Antoine Tenart <antoine.tenart@free-electrons.com> - 2015-08-19 10:20 +0200
csiph-web