From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PXA: Colibri320: Add M41T00 RTC support
Date: Sat, 31 Jul 2010 10:22:06 +0100 [thread overview]
Message-ID: <20100731092206.GC23886@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100731090554.GX17833@buzzloop.caiaq.de>
On Sat, Jul 31, 2010 at 11:05:54AM +0200, Daniel Mack wrote:
> Hmm, GPIOs for peripherals that are assembled on the module itself can
> safely be configured unconditionally as it is impossible to use them for
> anything else. For GPIOs that are allocted by a specific base board,
> things are different though, especially for the the Colibri eval board
> with it hundreds of jumpers on it. It's a convenience feature to have
> them free for general purpose use just by disabling a certain config
> directive.
It would probably make sense for their to be a primary table which at
least ensures that all pins are setup to safe default values. You
really don't want the unconnected pins left floating, especially if
they come out to some vulnerable connector or unconnected jumper pin.
I'd suggest they're configured as inputs but with a pull-up or pull-down,
not forgetting to consider the low power mode pull setting as well.
next prev parent reply other threads:[~2010-07-31 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 2:30 [PATCH] PXA: Colibri320: Add M41T00 RTC support Marek Vasut
2010-07-31 7:26 ` pieterg
2010-07-31 7:33 ` Marek Vasut
2010-07-31 9:05 ` Daniel Mack
2010-07-31 9:22 ` Russell King - ARM Linux [this message]
2010-08-04 6:25 ` Eric Miao
2010-07-31 10:34 ` Marek Vasut
2010-07-31 9:16 ` Russell King - ARM Linux
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=20100731092206.GC23886@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).