From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: "Leon Woestenberg" <leon.woestenberg@gmail.com>
Cc: linuxppc-dev@ozlabs.org, Bill Gatliff <bgat@billgatliff.com>
Subject: Re: Floating inputs on unused GPIO pins
Date: Tue, 28 Oct 2008 16:10:09 +0100 [thread overview]
Message-ID: <200810281610.12445.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <c384c5ea0810130640w7d0031f5j130c4edf83acccaf@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
Hi Leon,
sorry for the late reply.
On Monday 13 October 2008, Leon Woestenberg wrote:
> Hello Laurent,
>
> On Mon, Oct 13, 2008 at 3:12 PM, Bill Gatliff <bgat@billgatliff.com> wrote:
> > At least until someone plugs in that expansion module!
> >
> Bill's remark made a neuron connection in my head:
>
> Can you detect if the module is inserted or not? (By reading a known
> state of some pin)?
I can, although it's a bit more complex than that. The module is connected to the main board I2C bus so I can detect its presence by checking if chips connected to the bus are detected. Using a GPIO would have been much easier, but that's life :-)
> You could then configure the pins dynamically in your driver.
That's what I'm doing. As dynamic pin configuration requires board-specific knowledge in the device driver I would have liked to avoid that if possible.
Best regards, and thanks for your help.
--
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-28 15:10 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
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 [this message]
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=200810281610.12445.laurentp@cse-semaphore.com \
--to=laurentp@cse-semaphore.com \
--cc=bgat@billgatliff.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).