Hi Rahul, On Monday 26 of August 2013 14:43:02 Rahul Sharma wrote: > hdmi driver needs to change the parent of hdmi clock > to pixel clock or hdmiphy clock, based on the stability > of hdmiphy. This patch is exposing the mux for changing > the parent. > > Signed-off-by: Rahul Sharma <rahul.sha...@samsung.com> > --- > Documentation/devicetree/bindings/clock/exynos5420-clock.txt | 5 > +++++ drivers/clk/samsung/clk-exynos5420.c | > 5 ++++- 2 files changed, 9 insertions(+), 1 deletion(-) > > diff --git > a/Documentation/devicetree/bindings/clock/exynos5420-clock.txt > b/Documentation/devicetree/bindings/clock/exynos5420-clock.txt index > 5758a69..6f16aa8 100644 > --- a/Documentation/devicetree/bindings/clock/exynos5420-clock.txt > +++ b/Documentation/devicetree/bindings/clock/exynos5420-clock.txt > @@ -182,6 +182,11 @@ clock which they consume. > g3d 501 > smmu_mixer 502 > > + Mux ID > + ---------------------------- > + > + mout_hdmi 1024
Is there a need for such big hole between smm_mixer and this clock? I believe that based on the documentation, the total amount of clocks that can be defined may be approximated and some extra margin added, so you don't waste so much of numbering space and memory used for lookup array. Best regards, Tomasz -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
