From: Mark Howell <mhowell@northlink.com>
To: Mark Howell <mhowell@northlink.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] ARM: OMAP: mux: add config for 16xx SPI pins
Date: Wed, 30 Aug 2006 08:57:18 +0800 [thread overview]
Message-ID: <44F4E26E.4050701@northlink.com> (raw)
In-Reply-To: <44C7D8AC.7070505@northlink.com>
Mark Howell wrote:
> This patch adds pin mux info for the SPI master/slave interface on
> OMAP16xx. Data from OMAP 1611/1612 TRM and errata. Works for me on my
> 1611/H2 with current git kernel.
>
I have since spent some lab time with a scope and figured out that I
misunderstood the pull-up config bits in the mux definition structure
(they are inverted vs. what is actually written to the pull-up control
registers). The patch I posted before works, but it can be better.
I'll post a patch to set better default values for 16xx SPI pin mux
after I get a little more lab time. I don't think this is a burning
issue for anyone 'cept me, since eons had passed without anyone spec'ing
these pins for 16xx SPI anyway :-)
But this brings up a question... there are some other pins where I'm
suspicious of the default pull-up config in mux.c, such as for the
u-wire interface. Won't there be a bit of a power penalty for turning on
pull-up or pull-down when it isn't necessary? Is there some established
opinion or practice in this group regarding pin mux pull-up config to
which I can refer?
Cheers,
Mark.
next prev parent reply other threads:[~2006-08-30 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 21:03 [PATCH] ARM: OMAP: mux: add config for 16xx SPI pins Mark Howell
2006-08-30 0:57 ` Mark Howell [this message]
2006-08-30 8:19 ` 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=44F4E26E.4050701@northlink.com \
--to=mhowell@northlink.com \
--cc=linux-omap-open-source@linux.omap.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