The devm API usage in probe() simplifies error handling operation.
Since iclk is not used in the driver it is removed from wherever
not needed. The fclk naming is made uniform as per OMAP4 platform,
viz. timer1_fck, timer2_fck, ... in all relevant places which
include hwmod database. With this
On Mon, Apr 16, 2012 at 17:55:22, DebBarma, Tarun Kanti wrote:
The devm API usage in probe() simplifies error handling operation.
Since iclk is not used in the driver it is removed from wherever
not needed. The fclk naming is made uniform as per OMAP4 platform,
viz. timer1_fck, timer2_fck, ...
On Mon, Apr 16, 2012 at 8:23 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Mon, Apr 16, 2012 at 17:55:22, DebBarma, Tarun Kanti wrote:
The devm API usage in probe() simplifies error handling operation.
Since iclk is not used in the driver it is removed from wherever
not needed. The fclk
On Tue, Apr 17, 2012 at 01:20:49, DebBarma, Tarun Kanti wrote:
On Mon, Apr 16, 2012 at 8:23 PM, Hiremath, Vaibhav hvaib...@ti.com wrote:
On Mon, Apr 16, 2012 at 17:55:22, DebBarma, Tarun Kanti wrote:
The devm API usage in probe() simplifies error handling operation.
Since iclk is not used
