From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx6: Add IOMUX_CONFIG_SION flag to all GPIO pins
Date: Wed, 02 Oct 2013 08:06:20 +0200 [thread overview]
Message-ID: <524BB7DC.3070004@denx.de> (raw)
In-Reply-To: <1938105334.2320821.1380657041367.JavaMail.zimbra@advansee.com>
Hi Benoit, Eric, Otavio,
On 01/10/2013 21:50, Beno?t Th?baudeau wrote:
>>
>> You probably wouldn't just set SION on all pins, right? I suspect
>> that there'd be some ramification in terms of power consumption if
>> nothing else.
>
> Right. Well, instead of adding SION to the pin definition header files, then we
> could just add SION where needed on a per-pin basis, e.g.:
> ---
> imx_iomux_v3_setup_pad(MX6_PAD_NANDF_D1__GPIO_2_1 |
> IOMUX_CONFIG_SION << MUX_MODE_SHIFT);
> ---
>
> A helper macro could be defined in arch/arm/include/asm/imx-common/iomux-v3.h in
> order to simplify the writing, e.g.:
> ---
> #define MUX_MODE_SION (IOMUX_CONFIG_SION << MUX_MODE_SHIFT)
> ---
> imx_iomux_v3_setup_pad(MX6_PAD_NANDF_D1__GPIO_2_1 | MUX_MODE_SION);
> ---
>
> On the Linux side of things, the CONFIG field in the pinctrl DT bindings already
> provides bit 30 for SION. Hence, using MUX_MODE_SION like above would be close
> to Linux's pin config.
>
Agree, this is a better solution for the issue, and it is easier to be
tracked as setting SION for all pins.
Best regards,
Stefano
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2013-10-02 6:06 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
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 [this message]
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=524BB7DC.3070004@denx.de \
--to=sbabic@denx.de \
--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.