public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Pais, Allen" <allen.pais@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/2] omap: Disable GAIA I2C1/I2C4 internal pull-ups
Date: Tue, 2 Feb 2010 08:56:29 -0800	[thread overview]
Message-ID: <20100202165629.GS22747@atomide.com> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E94026AFAA3F2@dbde02.ent.ti.com>

* Pais, Allen <allen.pais@ti.com> [100201 18:56]:
> 
> ________________________________________
> From: Tony Lindgren [tony@atomide.com]
> Sent: Monday, February 01, 2010 7:53 PM
> To: Pais, Allen
> Cc: linux-omap@vger.kernel.org
> Subject: Re: [PATCH 1/2] omap: Disable GAIA I2C1/I2C4 internal pull-ups
> 
> Hi,
> 
> * Pais, Allen <allen.pais@ti.com> [100121 02:31]:
> > From 4044fcc9c517e86fbea9f7d3b15d5cf75a767476 Mon Sep 17 00:00:00 2001
> > From: Allen Pais <allen.pais@ti.com>
> > Date: Thu, 21 Jan 2010 21:00:04 +0530
> > Subject: [PATCH 1/2] omap: Disable GAIA I2C1/I2C4 internal pull-ups
> >
> > This patch disables GAIA I2C1 adn I2C4(SR) internal pull-up, to
> > use only the external HW resistor >=470 Ohm for the assured
> > functionality in HS mode.
> >
> > While testing the I2C in High Speed mode, it was discovered that
> > without a proper pull-up resistor, there is data corruption during
> > multi-byte transfer. RTC(time_set) test case was used for testing.
> >
> > From the analysis done, it was concluded that ideally we need a
> > pull-up of 1.6k Ohm(recomended) or atleast 470 Ohm or greater for
> > assured performance in HS mode.
> 
> Does this apply to 3630 only, or also 34xx? Is this safe to do
> always?
> 
> [Allen] Yes, it does apply to 36xx only. 

Sounds like then this configuration should be passed from the
board-*.c file in platform_data as the external pulls depend
on the board.
 
> BTW, once ready it hould be sent to Samuel Ortiz with linux-omap
> list Cc'd:
> 
> [Allen] i'll have it sent to Samuel also.

Thanks, we can't merge it yet though, see above.

Regards,

Tony

  reply	other threads:[~2010-02-02 16:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21 10:33 [PATCH 1/2] omap: Disable GAIA I2C1/I2C4 internal pull-ups Pais, Allen
2010-02-02  1:53 ` Tony Lindgren
2010-02-02  2:58   ` Pais, Allen
2010-02-02 16:56     ` Tony Lindgren [this message]
2010-02-02 21:40       ` Sonasath, Moiz
2010-02-03  1:16         ` Pais, Allen
2010-02-02  3:37 ` Paul Walmsley
2010-02-02 21:50   ` Sonasath, Moiz

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=20100202165629.GS22747@atomide.com \
    --to=tony@atomide.com \
    --cc=allen.pais@ti.com \
    --cc=linux-omap@vger.kernel.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