From: David Brownell <david-b@pacbell.net>
To: Steve Sakoman <sakoman@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Pin mux utility?
Date: Fri, 29 Aug 2008 10:17:39 -0700 [thread overview]
Message-ID: <200808291017.40151.david-b@pacbell.net> (raw)
In-Reply-To: <5e088bd90808290756k7c91d2dbu8e6593788d6a5d07@mail.gmail.com>
On Friday 29 August 2008, Steve Sakoman wrote:
> Is anyone aware of a utility to report the state of pin mux settings?
>
> I'd like to verify that u-boot is setting things up properly.
CONFIG_OMAP_MUX_WARNINGS helps for some definitions of "properly":
when Linux needs one setting, but the boot loader leaves a different
one, you get a warning. That's usually interpreted as u-boot doing
it wrong, except on devboards where the boot loader can't actually
know about all external hardware that might be hooked up (and how).
- Dave
next prev parent reply other threads:[~2008-08-29 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 14:56 Pin mux utility? Steve Sakoman
2008-08-29 15:01 ` Gadiyar, Anand
2008-08-29 15:05 ` Steve Sakoman
2008-08-29 15:08 ` Gadiyar, Anand
2008-08-29 17:17 ` David Brownell [this message]
2008-08-29 17:21 ` Igor Stoppa
2008-08-29 18:12 ` David Brownell
2008-09-02 22:51 ` Tony Lindgren
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=200808291017.40151.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@gmail.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