[PATCH] i2c: Race fix for i2c-mpc.c
Sylvain, Looks reasonable to me. Add a Signed-off-by: Kumar Gala line and sent to GregKH, lm-sensors guys. CC me if you would. - kumar On May 16, 2005, at 11:06 AM, Sylvain Munaut wrote: > Kumar Gala wrote: > > Sylvain, > > > > Are you really still using the OCP side of the driver?? Do we need a > > similar fix for the platform driver side? > > /me hits himself with a hammer > > Damn I included the wrong diff ... Sorry about that, the good one is > in attachment. > > > > No I don't use the OCP side but I changed both to stay coherent. I > don't > experience the problem myself, it's Asier who reported it and it > apparently mostly shows up on the second i2c bus (where I have nothing > on my hardware and anyway my bootloader init I2C beforehand ...). > > But the patch looks correct, when a bus is added, it should be ready to > be used. > > > > ??? Sylvain > > > > --- > i2c: Race fix for i2c-mpc.c > > The problem was that the clock speed and driver data is > initialized after the i2c adapter was added. This caused > the i2c bus to start working at a wrong speed. (Mostly > noticable on the second bus on mpc5200) > > With this patch we've tried to keep the i2c adapter > working perfectly all the time it is included in the system. > Initialize before added, Remove garbage after deleleted. > > > > Submitted-by: Asier Llano Palacios > Signed-off-by: Sylvain Munaut > --- >
[PATCH] i2c: Race fix for i2c-mpc.c
Kumar Gala wrote: > Sylvain, > > Are you really still using the OCP side of the driver? Do we need a > similar fix for the platform driver side? /me hits himself with a hammer Damn I included the wrong diff ... Sorry about that, the good one is in attachment. No I don't use the OCP side but I changed both to stay coherent. I don't experience the problem myself, it's Asier who reported it and it apparently mostly shows up on the second i2c bus (where I have nothing on my hardware and anyway my bootloader init I2C beforehand ...). But the patch looks correct, when a bus is added, it should be ready to be used. Sylvain --- i2c: Race fix for i2c-mpc.c The problem was that the clock speed and driver data is initialized after the i2c adapter was added. This caused the i2c bus to start working at a wrong speed. (Mostly noticable on the second bus on mpc5200) With this patch we've tried to keep the i2c adapter working perfectly all the time it is included in the system. Initialize before added, Remove garbage after deleleted. Submitted-by: Asier Llano Palacios Signed-off-by: Sylvain Munaut --- -- next part -- A non-text attachment was scrubbed... Name: i2c-mpc-racefix.diff Type: text/x-patch Size: 1314 bytes Desc: not available Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20050516/8f6195c9/attachment.bin
[PATCH] i2c: Race fix for i2c-mpc.c
Sylvain,
Are you really still using the OCP side of the driver? Do we need a
similar fix for the platform driver side?
- kumar
On May 16, 2005, at 1:24 AM, Sylvain Munaut wrote:
> i2c: Race fix for i2c-mpc.c
>
> The problem was that the clock speed and driver data is
> initialized after the i2c adapter was added. This caused
> the i2c bus to start working at a wrong speed. (Mostly
> noticable on the second bus on mpc5200)
>
> With this patch we've tried to keep the i2c adapter
> working perfectly all the time it is included in the system.
> Initialize before added, Remove garbage after deleleted.
>
>
>
> Submitted-by: Asier Llano Palacios
> Signed-off-by: Sylvain Munaut
> ---
> --- linux-2.6/drivers/i2c/busses/i2c-mpc.c? 2005-05-16
> 09:08:02.0 +0200
> +++ linux-2.6/drivers/i2c/busses/i2c-mpc.c? 2005-05-16
> 09:09:51.0 +0200
> @@ -333,6 +333,9 @@
> ??? } else
> ??? ??? i2c->irq = 0;
> ?
> +?? mpc_i2c_setclock(i2c);
> +?? ocp_set_drvdata(ocp, i2c);
> +
> ??? i2c->adap = mpc_ops;
> ??? i2c_set_adapdata(&i2c->adap, i2c);
> ?
> @@ -341,8 +344,6 @@
> ??? ??? goto fail_add;
> ??? }
> ?
> -?? mpc_i2c_setclock(i2c);
> -?? ocp_set_drvdata(ocp, i2c);
> ??? return result;
> ?
> ?? fail_add:
> @@ -358,8 +359,8 @@
> ?static void __devexit mpc_i2c_remove(struct ocp_device *ocp)
> ?{
> ??? struct mpc_i2c *i2c = ocp_get_drvdata(ocp);
> -?? ocp_set_drvdata(ocp, NULL);
> ??? i2c_del_adapter(&i2c->adap);
> +?? ocp_set_drvdata(ocp, NULL);
> ?
> ??? if (ocp->def->irq != OCP_IRQ_NA)
> ??? ??? free_irq(i2c->irq, i2c);
> ___
> Linuxppc-embedded mailing list
> Linuxppc-embedded at ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
[PATCH] i2c: Race fix for i2c-mpc.c
i2c: Race fix for i2c-mpc.c
The problem was that the clock speed and driver data is
initialized after the i2c adapter was added. This caused
the i2c bus to start working at a wrong speed. (Mostly
noticable on the second bus on mpc5200)
With this patch we've tried to keep the i2c adapter
working perfectly all the time it is included in the system.
Initialize before added, Remove garbage after deleleted.
Submitted-by: Asier Llano Palacios
Signed-off-by: Sylvain Munaut
---
--- linux-2.6/drivers/i2c/busses/i2c-mpc.c 2005-05-16 09:08:02.0
+0200
+++ linux-2.6/drivers/i2c/busses/i2c-mpc.c 2005-05-16 09:09:51.0
+0200
@@ -333,6 +333,9 @@
} else
i2c->irq = 0;
+ mpc_i2c_setclock(i2c);
+ ocp_set_drvdata(ocp, i2c);
+
i2c->adap = mpc_ops;
i2c_set_adapdata(&i2c->adap, i2c);
@@ -341,8 +344,6 @@
goto fail_add;
}
- mpc_i2c_setclock(i2c);
- ocp_set_drvdata(ocp, i2c);
return result;
fail_add:
@@ -358,8 +359,8 @@
static void __devexit mpc_i2c_remove(struct ocp_device *ocp)
{
struct mpc_i2c *i2c = ocp_get_drvdata(ocp);
- ocp_set_drvdata(ocp, NULL);
i2c_del_adapter(&i2c->adap);
+ ocp_set_drvdata(ocp, NULL);
if (ocp->def->irq != OCP_IRQ_NA)
free_irq(i2c->irq, i2c);
