From: plagnioj@jcrosoft.com (Jean-Christophe PLAGNIOL-VILLARD)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] at91sam9g45: fix i2c bus speed
Date: Thu, 23 Sep 2010 12:09:28 +0200 [thread overview]
Message-ID: <20100923100928.GX32018@game.jcrosoft.org> (raw)
In-Reply-To: <20100923093104.GA22397@n2100.arm.linux.org.uk>
On 10:31 Thu 23 Sep , Russell King - ARM Linux wrote:
> On Thu, Sep 23, 2010 at 11:22:36AM +0200, Peter Korsgaard wrote:
> > >>>>> "Nicolas" == Nicolas Ferre <nicolas.ferre@atmel.com> writes:
> >
> > Hi,
> >
> > Nicolas> By the way, I suspect that at91sam9g20 has the same issue
> > Nicolas> (400MHz core also)...
> >
> > Nicolas> We may also have a look at at91sam9g10 which embeds a 266MHz
> > Nicolas> core....
> >
> > Yes, but I don't have access that hw, so it's hard to know exact udelay
> > values. udelay=5 for 9g20 and udelay=3 for 9g10 probably aren't far off,
> > but it would be nice if someone with hw could test.
>
> udelay(5) should always give something approximating a 5us delay, as we
> calibrate this delay loop against the system timer. What I could believe
> is probably going on here is that writing to the hardware is adding
> additional delays - but that's nothing to do with the CPU speed itself.
yeah right
I guess as the amba bus and the other IP also is faster so the time spend to
change the state of the pio differ for a chip to an other
and we can not fix it easly so I do think it will be better to pass the speed
of the bus that we want from the board and then calcualte it depending on the
SOC
as we will only have this issue when using bitbanging but we can do the same
for hardware i2c
Best Regards,
J.
next prev parent reply other threads:[~2010-09-23 10:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 9:31 [PATCH] at91sam9g45: fix i2c bus speed Peter Korsgaard
2010-09-22 10:48 ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-22 11:08 ` Peter Korsgaard
2010-09-22 14:34 ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-22 14:54 ` Wolfgang Wegner
2010-09-22 16:09 ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-22 15:18 ` Peter Korsgaard
2010-09-22 16:05 ` Nicolas Ferre
2010-09-22 16:10 ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-22 16:06 ` Nicolas Ferre
2010-09-23 8:18 ` Nicolas Ferre
2010-09-23 9:22 ` Peter Korsgaard
2010-09-23 9:31 ` Russell King - ARM Linux
2010-09-23 10:09 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2010-09-23 10:24 ` Peter Korsgaard
2010-09-23 10:21 ` Peter Korsgaard
2010-09-23 10:36 ` Russell King - ARM Linux
2010-09-23 10:54 ` Peter Korsgaard
2010-09-23 11:16 ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-23 11:32 ` Peter Korsgaard
2010-09-23 12:00 ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-23 11:07 ` Jean-Christophe PLAGNIOL-VILLARD
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=20100923100928.GX32018@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=linux-arm-kernel@lists.infradead.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).