From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: "Leon Woestenberg" <leon.woestenberg@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Floating inputs on unused GPIO pins
Date: Mon, 13 Oct 2008 13:04:41 +0200 [thread overview]
Message-ID: <200810131304.41435.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <c384c5ea0810130308q5cfa2c2ld8ea5eafec99bba3@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1612 bytes --]
Hi Leon,
On Monday 13 October 2008, Leon Woestenberg wrote:
> Hello Laurent,
>
> On Mon, Oct 13, 2008 at 11:56 AM, Laurent Pinchart
> <laurentp@cse-semaphore.com> wrote:
> > our hardware engineer asked me to make sure all unused GPIO pins are
> > configured as outputs to avoid floating inputs. He got theory on his side
> > (floating inputs can lead to higher current consumption, metastability or
> > even permanent damage), but I'd like to ask the list for practical
> > feedback.
> >
> Ideally, configure them as inputs or tri-state (both mean high
> impedance), and do use pull-down or -up resistors.
As I explained in my mail to Geert, that's not really an option. The GPIO pins are connected to an optional expansion module. When the module is plugged in the pins have dedicated functions. When the module is not present they are by default floating inputs. That's the case our hardware engineer is concerned about.
> Now, the answer might be different when your pins are not connected.
> Check on the processor if internal pull resistors are present. If so,
> use as input. If not, then your h/w engineer *may* have a point, not
> sure on that though.
There are no internal pull-up or pull-down resistors on the MPC8248 GPIO pins. I know our hardware engineer has a valid point theoretically. Does the point stand practically, or does the MPC8248 "state-of-the-art"(tm)(c)(whatever) technology make floating inputs safe ?
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussee de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
F +32 (2) 387 42 75
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-13 11:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 9:56 Floating inputs on unused GPIO pins Laurent Pinchart
2008-10-13 10:03 ` Geert Uytterhoeven
2008-10-13 11:00 ` Laurent Pinchart
2008-10-13 10:08 ` Leon Woestenberg
2008-10-13 11:04 ` Laurent Pinchart [this message]
2008-10-13 11:44 ` Leon Woestenberg
2008-10-13 13:12 ` Bill Gatliff
2008-10-13 13:40 ` Leon Woestenberg
2008-10-28 15:10 ` Laurent Pinchart
2008-10-14 11:07 ` [OT] " Gabriel Paubert
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=200810131304.41435.laurentp@cse-semaphore.com \
--to=laurentp@cse-semaphore.com \
--cc=leon.woestenberg@gmail.com \
--cc=linuxppc-dev@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).