From: Sylvain Munaut <tnt@246tNt.com>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: Asier Llano Palacios <a.llano@usyscom.com>,
ML linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] i2c: Race fix for i2c-mpc.c
Date: Mon, 16 May 2005 18:06:21 +0200 [thread overview]
Message-ID: <4288C4FD.8080104@246tNt.com> (raw)
In-Reply-To: <5fe12cfac05d60b8af016382594e50db@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
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 <tnt@246tNt.com>
---
[-- Attachment #2: i2c-mpc-racefix.diff --]
[-- Type: text/x-patch, Size: 1314 bytes --]
--- linux-2.6/drivers/i2c/busses/i2c-mpc.c 2005-05-16 09:47:10.000000000 +0200
+++ linux-2.6-mpc52xx/drivers/i2c/busses/i2c-mpc.c 2005-05-16 17:50:18.000000000 +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);
@@ -430,6 +431,9 @@
goto fail_irq;
}
+ mpc_i2c_setclock(i2c);
+ dev_set_drvdata(device, i2c);
+
i2c->adap = mpc_ops;
i2c_set_adapdata(&i2c->adap, i2c);
i2c->adap.dev.parent = &pdev->dev;
@@ -438,8 +442,6 @@
goto fail_add;
}
- mpc_i2c_setclock(i2c);
- dev_set_drvdata(device, i2c);
return result;
fail_add:
@@ -456,8 +458,8 @@
{
struct mpc_i2c *i2c = dev_get_drvdata(device);
- dev_set_drvdata(device, NULL);
i2c_del_adapter(&i2c->adap);
+ dev_set_drvdata(device, NULL);
if (i2c->irq != 0)
free_irq(i2c->irq, i2c);
next prev parent reply other threads:[~2005-05-16 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 6:24 [PATCH] i2c: Race fix for i2c-mpc.c Sylvain Munaut
2005-05-16 15:30 ` Kumar Gala
2005-05-16 16:06 ` Sylvain Munaut [this message]
2005-05-17 16:12 ` Kumar Gala
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4288C4FD.8080104@246tNt.com \
--to=tnt@246tnt.com \
--cc=a.llano@usyscom.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).