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
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
On Mon, 27 Aug 2012, Hiremath, Vaibhav wrote:
On Mon, Aug 27, 2012 at 22:50:12, Paul Walmsley wrote:
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
On Tue, Aug 28, 2012 at 00:06:45, Paul Walmsley wrote:
On Mon, 27 Aug 2012, Hiremath, Vaibhav wrote:
On Mon, Aug 27, 2012 at 22:50:12, Paul Walmsley wrote:
Is the dcan driver present in v3.6-rc kernels?
Multiple versions have been submitted already, I have validated using them.
