* Shubhrajyoti shubhrajy...@ti.com [120621 02:35]:
On Thursday 21 June 2012 12:50 PM, Tony Lindgren wrote:
* Shubhrajyoti shubhrajy...@ti.com [120621 00:08]:
On Wednesday 20 June 2012 03:59 PM, Tony Lindgren wrote:
See the comments regarding driver specific resets in hwmod code.
you mean
On Wednesday 20 June 2012 03:59 PM, Tony Lindgren wrote:
See the comments regarding driver specific resets in hwmod code.
you mean omap_hwmod.c
The way to set this up is to have a shared inline function in
i2c-omap.h that both the driver and hwmod code can use.
hwmod reset function uses oh
* Shubhrajyoti shubhrajy...@ti.com [120621 00:08]:
On Wednesday 20 June 2012 03:59 PM, Tony Lindgren wrote:
See the comments regarding driver specific resets in hwmod code.
you mean omap_hwmod.c
The way to set this up is to have a shared inline function in
i2c-omap.h that both the driver
On Thursday 21 June 2012 12:50 PM, Tony Lindgren wrote:
* Shubhrajyoti shubhrajy...@ti.com [120621 00:08]:
On Wednesday 20 June 2012 03:59 PM, Tony Lindgren wrote:
See the comments regarding driver specific resets in hwmod code.
you mean omap_hwmod.c
The way to set this up is to have a shared
* Shubhrajyoti D shubhrajy...@ti.com [120618 07:35]:
The reset in the driver at init is not needed anymore as the
following patch has removed the HWMOD_INIT_NO_RESET flag.
6d3c55f [OMAP: hwmod: fix the i2c-reset timeout during bootup]
This patch does the following
-removes the reset from
The reset in the driver at init is not needed anymore as the
following patch has removed the HWMOD_INIT_NO_RESET flag.
6d3c55f [OMAP: hwmod: fix the i2c-reset timeout during bootup]
This patch does the following
-removes the reset from the probe and implements a omap_i2c_reset
function to reset.
