[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <79CD15C6BA57404B839C016229A409A83EA99396@DBDE01.ent.ti.com>
Date: Mon, 27 Aug 2012 18:02:35 +0000
From: "Hiremath, Vaibhav" <hvaibhav@...com>
To: Paul Walmsley <paul@...an.com>
CC: "linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Tony Lindgren <tony@...mide.com>,
"Cousson, Benoit" <b-cousson@...com>,
Grant Likely <grant.likely@...retlab.ca>,
Rob Herring <robherring2@...il.com>
Subject: RE: [PATCH] ARM: AM33XX: clock: Add dcan clock aliases for
device-tree
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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists