On Mon, Aug 27, 2012 at 22:50:12, Paul Walmsley wrote: > Hi > > On Mon, 27 Aug 2012, Vaibhav Hiremath wrote: > > > Currently, the device names for the dcan module follows the > > format "dcan.X", where 'X' is the dcan instance number. > > On other side, driver may request for clock with/without con_id > > and dev_id, and it is expected that platform should respect this > > request and return the requested clock handle. > > > > Now, when using device tree, the format of the device name created > > by OF layer is different, "<reg-address>.<device-name>", > > assuming that the device-tree "reg" property is specified. > > This causes the look-up failure for clock node in dcan driver > > > > To fix this add new dcan clock alias for using device-tree. > > Is the dcan driver present in v3.6-rc kernels? Multiple versions have been submitted already, I have validated using them. Irrespective of this, it is independent change and required for the driver. Thanks, Vaibhav -- 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
