On 03/09/2018 02:01 PM, Krzysztof Kozlowski wrote:
>> diff --git a/arch/arm/boot/dts/exynos5250-snow-common.dtsi b/arch/arm/boot/dts/exynos5250-snow-common.dtsi
>> index bdf59dd3654b..932a00cfd716 100644
>> --- a/arch/arm/boot/dts/exynos5250-snow-common.dtsi
>> +++ b/arch/arm/boot/dts/exynos5250-snow-common.dtsi
>> @@ -9,6 +9,7 @@
>> #include <dt-bindings/clock/maxim,max77686.h>
>> #include <dt-bindings/interrupt-controller/irq.h>
>> #include <dt-bindings/input/input.h>
>> +#include <dt-bindings/sound/samsung-i2s.h>
>> #include "exynos5250.dtsi"
>>
>> / {
>> @@ -523,6 +524,9 @@
>> };
>>
>> &i2s0 {
>> + assigned-clocks = <&i2s0 CLK_I2S_RCLK_SRC>;
>> + assigned-clock-parents = <&clock_audss EXYNOS_I2S_BUS>;
>> + #clock-cells = <1>;
>
> Shouldn't this be property of exynos5250.dtsi? Along with clock-output-names?
Hmm, it should be safe to move it there. By specifying this property or not
we can control whether the I2S clocks are exposed or not. If we move it to
exynos5250.dtsi the clocks we always be exposed. But should be the right thing
to do anyway. I will post v3.
Of course we recently made the clock-output-names property deprecated, it will
not bee needed any more. It was there just to ensure the clk names are unique.
--
Regards,
Sylwester
--
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
