Jan Weitzel <j.weitzel@xxxxxxxxx> writes:
> omap4430 get i2c timeouts at each access after an NACK message.
> OMAP_I2C_FLAG_RESET_REGS_POSTIDLE fix it.
We need a little better changelog here. Specifically, *why* does this
flag fix the problem? What exactly is going wrong such that this fix
is needed.
Does this happen all the time? only when off-mode is used? etc.
Looking closer at how this flag is used in the driver, I think the
driver's usage of runtime PM is a bit broken. I'm not sure if it's
related to this problem, but I'll send a short series in a little bit to
clean up the runtime PM usage, and get rid of the dev->idle flag which
duplicates usage counting already provided by runtime PM.
Kevin
> Signed-off-by: Jan Weitzel <j.weitzel@xxxxxxxxx>
> Tested-by: Andy Green <andy.green@xxxxxxxxxx>
> Acked-by: Andy Green <andy.green@xxxxxxxxxx>
> ---
> Works on top of tmlind linux-omap-2.6.git
> v3: commit message
> v2: add Tested-by / Acked-by
>
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> index 5f4a1b2..3d3b4f4 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> @@ -2130,7 +2130,8 @@ static struct omap_hwmod_class omap44xx_i2c_hwmod_class = {
> };
>
> static struct omap_i2c_dev_attr i2c_dev_attr = {
> - .flags = OMAP_I2C_FLAG_BUS_SHIFT_NONE,
> + .flags = OMAP_I2C_FLAG_BUS_SHIFT_NONE |
> + OMAP_I2C_FLAG_RESET_REGS_POSTIDLE,
> };
>
> /* i2c1 */
--
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
