From: Prafulla Wadaskar <prafulla@marvell.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] arm/km: speed up i2c access for keymile boards
Date: Wed, 8 Feb 2012 01:47:51 -0800 [thread overview]
Message-ID: <F766E4F80769BD478052FB6533FA745D1A2F35BDAD@SC-VEXCH4.marvell.com> (raw)
In-Reply-To: <4F32371C.5020501@keymile.com>
> -----Original Message-----
> From: Holger Brunck [mailto:holger.brunck at keymile.com]
> Sent: 08 February 2012 14:20
> To: Prafulla Wadaskar
> Cc: u-boot at lists.denx.de; Valentin Longchamp; Heiko Schocher
> Subject: Re: [PATCH 1/2] arm/km: speed up i2c access for keymile
> boards
>
> Hi Prafulla,
>
> On 12/14/2011 04:31 PM, Holger Brunck wrote:
> > We don't need 3us delay for our i2c bus. Decrease it to 1us.
> > It would also be possible to use 100ns in the future, but
> > currently kirkwood has no ndelay implementation.
> >
> > Signed-off-by: Holger Brunck <holger.brunck@keymile.com>
> > Cc: Valentin Longchamp <valentin.longchamp@keymile.com>
> > Cc: Prafulla Wadaskar <prafulla@marvell.com>
> > Cc: Heiko Schocher <hs@denx.de>
> > ---
> > include/configs/km/km_arm.h | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
>
> can you pull these two small updates for km_arm or is something
> misssing?
Applied both to u-boot-marvell.git master branch
Regards..
Prafulla . . .
prev parent reply other threads:[~2012-02-08 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 15:31 [U-Boot] [PATCH 1/2] arm/km: speed up i2c access for keymile boards Holger Brunck
2011-12-14 15:31 ` [U-Boot] [PATCH 2/2] arm/km: checkpatch cleanup Holger Brunck
2011-12-15 6:31 ` Heiko Schocher
2011-12-15 6:30 ` [U-Boot] [PATCH 1/2] arm/km: speed up i2c access for keymile boards Heiko Schocher
2012-02-08 8:49 ` Holger Brunck
2012-02-08 9:47 ` Prafulla Wadaskar [this message]
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=F766E4F80769BD478052FB6533FA745D1A2F35BDAD@SC-VEXCH4.marvell.com \
--to=prafulla@marvell.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.