From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] i.MX6 (DQ/DLS): use macros for mux and pad declarations
Date: Mon, 18 Nov 2013 12:04:39 +0100 [thread overview]
Message-ID: <5289F447.9080006@denx.de> (raw)
In-Reply-To: <1384385780-11021-2-git-send-email-eric.nelson@boundarydevices.com>
Hi Eric,
On 14/11/2013 00:36, Eric Nelson wrote:
> This allows the use of either or both declarations from
> the files mx6q_pins.h and mx6dl_pins.h.
>
> All board files should include <asm/arch/mx6-pins.h>
> with one of the following defined in boards.cfg
> MX6Q - for boards targeting i.MX6Q or i.MX6D
> MX6DL - for boards targeting i.MX6DL
> MX6S - for boards targeting i.MX6S
> MX6QDL - for boards that support any of the above with
> run-time detection
>
> Pad declarations will be MX6_PAD_x for single-variant boards
> and MX6Q_PAD_x and MX6DL_PAD_x for boards supporting both
> processor classes.
>
> Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com>
> ---
Thanks Eric, this is the way we have already discussed how to set the
pinmux at runtime.
Acked-by: Stefano Babic <sbabic@denx.de>
Best regards,
Stefano Babic
--
=====================================================================
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-11-18 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 23:36 [U-Boot] [PATCH 0/2] i.MX6 (DQ/DLS): use macros for mux and pad declarations Eric Nelson
2013-11-13 23:36 ` [U-Boot] [PATCH 1/2] " Eric Nelson
2013-11-18 11:04 ` Stefano Babic [this message]
2013-12-17 16:13 ` Stefano Babic
2013-11-13 23:36 ` [U-Boot] [PATCH 2/2] i.MX6DQ/DLS: whitespace: Align MX6_PAD_DECL columns Eric Nelson
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=5289F447.9080006@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.