On Saturday 19 July 2014 01:23:15 Chanwoo Choi wrote:
> If don't add new compatible including specific exynos version,
> I would add new 'adc-needs-sclk' property with existing 'exynos-adc-v2'
> compatible name.
>
>
> Dear Naveen, Tomasz,
>
> If existing exynos-adc driver add just one property for 'sclk_adc'
> as following, exynos-adc could not include the exynos version
> in compatible name.
>
> I need your opinion about it.
>
> adc: adc@126C0000 {
> compatible = "samsung,exynos-adc-v2";
> reg = <0x126C0000 0x100>, <0x10020718 0x4>;
> interrupts = <0 137 0>;
> clock-names = "adc", "sclk_adc";
> clocks = <&cmu CLK_TSADC>, <&cmu CLK_SCLK_TSADC>;
> + adc-needs-sclk;
> #io-channel-cells = <1>;
> io-channel-ranges;
> }
How about just making it an optional clock? That would be much
easier because then you can simply see if the clock itself is
there and use it, or otherwise ignore it.
Arnd
--
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
