On 10.12.2015 09:49, Chanwoo Choi wrote:
> Hi,
>
(...)
>>
>>> +
>>> + bus_dmc: bus_dmc {
>>> + compatible = "samsung,exynos-bus";
>>> + clocks = <&cmu_dmc CLK_DIV_DMC>;
>>> + clock-names = "bus";
>>> + operating-points-v2 = <&bus_dmc_opp_table>;
>>> + status = "disabled";
>>> + };
>>> +
>>> + bus_dmc_opp_table: opp_table0 {
>>> + compatible = "operating-points-v2";
>>> + opp-shared;
>>> +
>>> + opp00 {
>>
>> Maybe use convention with frequency, like:
>> opp@50000000
>> This also used in opp.txt examples.
>
> In the Documentations/devicetree/bindings/opp/opp.txt,
> the example uses the 'opp@0x'. I check the opp.txt of Linux 4.4-rc4.
Yes, it was changed by Viresh in "PM / OPP: Rename OPP nodes as
opp@<opp-hz>". You can find the most actual bindings in linux-next.
Best regards,
Krzysztof
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
