From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 01/11] ARM: tegra: pinctrl: remove func_safe
Date: Fri, 14 Mar 2014 12:45:21 -0600 [thread overview]
Message-ID: <53234E41.30304@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ3wE1Nwa1yXWPvr57RvrCEzvdNNRp-CJf+u=_a=9+9hGw@mail.gmail.com>
On 03/14/2014 12:22 PM, Simon Glass wrote:
> Hi Stephen,
>
> On 13 March 2014 11:41, Stephen Warren <swarren@wwwdotorg.org> wrote:
>>
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> This field isn't used anywhere, so remove it. Note that PIN() macros are
>> left unchanged for now, to avoid many diffs to them; later commits will
>> completely rewrite them just one time.
>>
> I recall this being a way of putting pins into a 'safe' state which is
> not incompatible with other changes. I suppose we could look up the
> details, but if it isn't actually used, we should drop it.
Yes, that's what the data is for.
However, I think the place to use that data is when constructing the
pinmux table for a board, when one is selecting which mux function to
use for each pin. This happens offline rather than at run-time, so the
data isn't needed at run-time.
next prev parent reply other threads:[~2014-03-14 18:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 17:41 [U-Boot] [PATCH 00/11] ARM: tegra: pinmux driver cleanup Stephen Warren
2014-03-13 17:41 ` [U-Boot] [PATCH 01/11] ARM: tegra: pinctrl: remove func_safe Stephen Warren
2014-03-14 18:22 ` Simon Glass
2014-03-14 18:45 ` Stephen Warren [this message]
2014-03-13 17:41 ` [U-Boot] [PATCH 02/11] ARM: tegra: pinctrl: remove vddio Stephen Warren
2014-03-14 18:23 ` Simon Glass
2014-03-13 17:41 ` [U-Boot] [PATCH 03/11] ARM: tegra: pinctrl: make pmux_func values consistent on Tegra20 Stephen Warren
2014-03-14 18:25 ` Simon Glass
2014-03-13 17:42 ` [U-Boot] [PATCH 04/11] ARM: tegra: prototype pinmux_init() in board.h Stephen Warren
2014-03-14 18:26 ` Simon Glass
2014-03-13 17:42 ` [U-Boot] [PATCH 05/11] ARM: tegra: pinctrl: remove duplication Stephen Warren
2014-03-14 19:37 ` Simon Glass
2014-03-20 19:57 ` Stephen Warren
2014-03-21 1:25 ` Simon Glass
2014-03-21 4:07 ` Stephen Warren
2014-03-13 17:42 ` [U-Boot] [PATCH 06/11] ARM: tegra: reduce public pinmux API Stephen Warren
2014-03-14 19:39 ` Simon Glass
2014-03-13 17:42 ` [U-Boot] [PATCH 07/11] ARM: tegra: pinmux naming consistency fixes Stephen Warren
2014-03-14 20:15 ` Simon Glass
2014-03-14 23:43 ` Stephen Warren
2014-03-20 19:08 ` Stephen Warren
2014-03-13 17:42 ` [U-Boot] [PATCH 08/11] ARM: tegra: Tegra20 pinmux cleanup Stephen Warren
2014-03-13 17:42 ` [U-Boot] [PATCH 09/11] ARM: tegra: Tegra30 " Stephen Warren
2014-03-13 17:42 ` [U-Boot] [PATCH 10/11] ARM: tegra: Tegra114 " Stephen Warren
2014-03-13 17:42 ` [U-Boot] [PATCH 11/11] ARM: tegra: Tegra124 " Stephen Warren
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=53234E41.30304@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox