From: Tony Lindgren <tony@atomide.com>
To: Leon Woestenberg <leon.woestenberg@gmail.com>
Cc: "Sonasath, Moiz" <m-sonasath@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Pais, Allen" <allen.pais@ti.com>,
"Pandita, Vikram" <vikram.pandita@ti.com>
Subject: Re: [PATCH V3 2/2]OMAP: Disable internal I2C pull-ups in OMAP3630
Date: Thu, 10 Jun 2010 08:56:43 +0300 [thread overview]
Message-ID: <20100610055643.GL32208@atomide.com> (raw)
In-Reply-To: <AANLkTimwvegsWDtS7v-aZmjCHyl46ATcgo5wGWCm3xn-@mail.gmail.com>
* Leon Woestenberg <leon.woestenberg@gmail.com> [100609 22:20]:
> Hello Tony,
>
> On Tue, Jun 8, 2010 at 12:04 PM, Tony Lindgren <tony@atomide.com> wrote:
> > Because of this, 3630 boards should have the mux register pull-ups disabled,
> > and only use the dedicated I2C pull-ups. In theory external pull-ups should
> > not be needed. The value configured for the dedicated I2C pull-ups depends
> > on the connected I2C device, and the number of devices.
> >
> If the internal pull-ups are disabled, why are external pull-ups not needed?
There are two omap internal pull-ups available: The iopad mux pull-ups and the
I2C specific pull-ups. Only the I2C specific ones should be used.
Regards,
Tony
prev parent reply other threads:[~2010-06-10 5:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1267211687-23551-1-git-send-email-m-sonasath@ti.com>
2010-03-22 22:44 ` [PATCH V3 2/2]OMAP: Disable internal I2C pull-ups in OMAP3630 Sonasath, Moiz
2010-06-08 10:04 ` Tony Lindgren
2010-06-08 23:29 ` Woodruff, Richard
2010-06-09 12:23 ` Tony Lindgren
2010-06-09 19:26 ` Leon Woestenberg
2010-06-10 5:56 ` Tony Lindgren [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=20100610055643.GL32208@atomide.com \
--to=tony@atomide.com \
--cc=allen.pais@ti.com \
--cc=leon.woestenberg@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=m-sonasath@ti.com \
--cc=vikram.pandita@ti.com \
/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).