On Tue, Feb 09, 2016 at 06:10:40PM +0100, Maxime Ripard wrote:
>>It seems that the other compatible strings are there for historical
>>reasons. Why do you need a new one with such a specific name?
>>
>>It would have been more sensible to add a generic compatible string as
>>"allwinner,apb-gates", letting the removal of the other strings for a
>>later patch...
>
>Yeah, it's a good idea, and it's probably time that we move to that.
>
>However, I'd like to keep per-soc and per-clocks compatibles in the
>DT, in case we need to protect a clock in the future. That doesn't
>prevent to have two compatibles thoughe, the specific and the generic.
>
So now I'm not sure what you mean. You suggest that I should keep using
specific (sun8i_h3_apb0) or change to generic (apb-gates) in my patch?
Both.
To have something like that:
compatible = "allwinner,sun8i-h3-apb0-gates-clk", "allwinner,sun4i-a10-gates-clk";
sun4i-a10-gates-clk being the generic compatible that we would use,
and we can always match against the h3 specific compatible if we need
to have a different behaviour.
This seems like a good idea to me but since this is new thing anyways
(other sunxi SoCs don't do this right now) shouldn't we introduce other
more generic name for generic clock (like "allwinner,apb-gates"
mentioned earlier, or maybe "allwinner,simple-apb-gates")?
Also, wouldn't this be cleaner if I use only specific compatible string
right now and provide separate patch that adds generic compatible string
to all current SoCs at once? The downside of this is that it's easier to
get merge conflicts unless I wait for applying this patchset.
Best regards,
Krzysztof Adamski
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
