Hi Paul,
On Friday 09 March 2012 12:21 PM, Paul Walmsley wrote:
On Thu, 8 Mar 2012, Grant Likely wrote:
Yes, absolutely use separate compatible values. It is always important
to be specific as to the silicon implementing the IP.
In that case, it is probably best to use the full chip name in the
compatible string, e.g., omap2420 or omap2430 rather than just "omap2".
Since omap2420 and omap2430 have different MMC controllers (and these
bindings only cover the hsmmc controller used in 2430 and beyond, I
haven't done the bindings for the legacy one yet), the idea was
to differentiate between omap2420 and omap2430 by using
compatible of "ti,omap2-hsmmc" for the High-Speed controller used in
OMAP2 (2430) and "ti,omap2-mmc" for the legacy one used in OMAP2 (2420).
Does that sound good to you?
Particularly in the case of "OMAP3," which is a largely meaningless group
these days with AM33xx, OMAP34xx, OMAP36xx, and AM3517, many of which are
quite different from each other...
But these bindings are specific and limited to HSMMC module which is
not quite different in the different SoC variants. There is a single
driver to handle hsmmc module on all the SoCs which does not need to
differentiate which SoC it is on.
regards,
Rajendra
- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
