From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx6: Add IOMUX_CONFIG_SION flag to all GPIO pins
Date: Tue, 01 Oct 2013 08:56:11 -0700 [thread overview]
Message-ID: <524AF09B.7040505@boundarydevices.com> (raw)
In-Reply-To: <524AE107.1050404@denx.de>
Hi Stefano,
On 10/01/2013 07:49 AM, Stefano Babic wrote:
> Hi Eric,
>
> On 01/10/2013 16:26, Eric Nelson wrote:
>
>> I'm not sure where you're seeing this in the RM, but in
>> order to read the pad state when not configured as an input,
>> the SION bit needs to be set in the pad mux register on i.MX51/53.
>
> I have checked inside the "37.3.2.2 GPIO Write" for i.MX53 and "
> 35.4.2.1 Read Value from Pad" for i:MX51, I have not read anything about
> SION. If someone has found where it is described, please mail !
>
That documentation seems to imply that there's no dependency
(i.e. there's no reference to SION), but I think that's an omission.
>>
>> FWIW, this also works when not muxed as a GPIO, which is really
>> handy for verifying that a PWM is toggling, et cetera.
>
> Well, if you have directly tested it, it is better proofed as by the
> manuals..then we need the same fix for i.MX51/i.MX53, too.
>
I've tested this many times, since it's a really handy way of
debugging hardware setups.
That said, I'm not sure that there's a huge difference between
a single patch or multiple patches for each arch unless there's
some functionality dependent on being able to read the actual
value of a pin configured as a GPIO output.
Did I miss something in this thread that does actually require
that ability? It seems a pretty obscure thing in the normal case
to drive an output without confidence that it will succeed.
Regards,
Eric
next prev parent reply other threads:[~2013-10-01 15:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 22:15 [U-Boot] [PATCH] mx6: Add IOMUX_CONFIG_SION flag to all GPIO pins Otavio Salvador
2013-10-01 8:33 ` Stefano Babic
2013-10-01 12:01 ` Otavio Salvador
2013-10-01 12:43 ` Marek Vasut
2013-10-01 13:08 ` Otavio Salvador
2013-10-01 14:21 ` Eric Nelson
2013-10-01 13:13 ` Stefano Babic
2013-10-01 14:26 ` Eric Nelson
2013-10-01 14:49 ` Stefano Babic
2013-10-01 15:56 ` Eric Nelson [this message]
2013-10-01 16:10 ` Stefano Babic
2013-10-01 16:17 ` Eric Nelson
2013-10-01 19:50 ` Benoît Thébaudeau
2013-10-01 20:01 ` Otavio Salvador
2013-10-01 20:21 ` Benoît Thébaudeau
2013-10-01 20:25 ` Fabio Estevam
2013-10-01 21:29 ` Eric Nelson
2013-10-02 6:06 ` Stefano Babic
2013-10-01 16:23 ` Benoît Thébaudeau
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=524AF09B.7040505@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--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.