From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tegra: implement pinmux_avoid_func()
Date: Tue, 22 Jan 2013 14:26:45 -0700 [thread overview]
Message-ID: <50FF0415.4080601@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ37xEYLO7f_0JZnwEeypvqKd6EuAaJi+PEP1P55Pdk_YQ@mail.gmail.com>
On 01/22/2013 02:13 PM, Simon Glass wrote:
> Hi Stephen,
>
> On Tue, Jan 22, 2013 at 8:21 AM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> This selects the "safe" (non-conflicting) mux function for a pin group
>> if the current setting matches the specified function.
>>
>> Many signals can be routed to or from multiple different groups. Each
>> signal must be routed to or from only a single group at a given time.
>> Hence, if we program a particular group for a function, we must ensure
>> no other group is programmed to that same function first. This API
>> makes this easy.
>
> What is the intended use of this function? (sorry, yes, I am confused :-)
It's a safer way of doing this:
"tegra: pinmux: fix FUNCMUX_NDFLASH_KBC_8_BIT"
http://lists.denx.de/pipermail/u-boot/2013-January/144612.html
i.e. it address the concerns I raised here:
http://lists.denx.de/pipermail/u-boot/2013-January/144713.html
next prev parent reply other threads:[~2013-01-22 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 16:21 [U-Boot] [PATCH] tegra: implement pinmux_avoid_func() Stephen Warren
2013-01-22 21:13 ` Simon Glass
2013-01-22 21:26 ` Stephen Warren [this message]
2013-01-22 21:42 ` Simon Glass
2013-01-22 22:14 ` Stephen Warren
2013-01-23 0:03 ` Simon Glass
2013-01-23 0:21 ` Stephen Warren
2013-01-23 0:26 ` Simon Glass
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=50FF0415.4080601@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.