On Tue, May 20, 2014 at 1:04 AM, Rajendra Nayak <rnayak@xxxxxx> wrote: > So we are back to checking revisions based on idcode register then? > This patch was posted almost a year back and was shot down by you > included saying we need to use dt compatibles for it. > > https://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg93136.html No, even thought it looks like, we are not intending to here. we are fixing a sysfs break. soc_is_dra7xx() is still based on machine_of_ compatible - we have'nt touched that here. What is taking place at the moment is that /sys/devices/soc0/ sysfs entries are being populated in same way as AM437x and other DT only platforms. Currently we follow the same style as non-dt code as OMAP3 still co-exist DT+non-DT - we have not yet introduced a new driver for soc device - but once we go full DT, we probably should do that at the root of the entire dt tree (similar to what tegra has done) and populare soc sysfs with proper values. Now, if that generic driver decides to use only OF-information for revision, That is good as well -> so far, there has been no attempt to support such a revision binding (despite our discussion). Regards, Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
