All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 5/5] board: ti: dra76: mux wakeup2 as gpio1_2
Date: Wed, 20 Dec 2017 20:59:40 +0530	[thread overview]
Message-ID: <20171220152940.27950-6-lokeshvutla@ti.com> (raw)
In-Reply-To: <20171220152940.27950-1-lokeshvutla@ti.com>

From: Tomi Valkeinen <tomi.valkeinen@ti.com>

gpio1_2 is used for HPD interrupt with DRA76's DVI add-on board, so mux
the pin as gpio and PIN_INPUT.

Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
---
 board/ti/dra7xx/mux_data.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/board/ti/dra7xx/mux_data.h b/board/ti/dra7xx/mux_data.h
index 3c3a19a0e1..b5dcaa584a 100644
--- a/board/ti/dra7xx/mux_data.h
+++ b/board/ti/dra7xx/mux_data.h
@@ -882,7 +882,7 @@ const struct pad_conf_entry dra76x_core_padconf_array[] = {
 	{I2C2_SCL, (M1 | PIN_INPUT_PULLUP)},	/* i2c2_scl.hdmi1_ddc_sda */
 	{WAKEUP0, (M14 | PIN_OUTPUT)},	/* N/A.gpio1_0 */
 	{WAKEUP1, (M14 | PIN_OUTPUT)},	/* N/A.gpio1_1 */
-	{WAKEUP2, (M1 | PIN_OUTPUT)},	/* N/A.sys_nirq2 */
+	{WAKEUP2, (M14 | PIN_INPUT)},	/* N/A.gpio1_2 */
 	{WAKEUP3, (M1 | PIN_OUTPUT)},	/* N/A.sys_nirq1 */
 };
 
-- 
2.15.1

      parent reply	other threads:[~2017-12-20 15:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20 15:29 [U-Boot] [PATCH v2 0/5] arm: ti: misc updates and bug fixes Lokesh Vutla
2017-12-20 15:29 ` [U-Boot] [PATCH v2 1/5] configs: k2g_evm: Allocate more space for u-boot Lokesh Vutla
2017-12-20 15:29 ` [U-Boot] [PATCH v2 2/5] board: TI K2G: FC SoC 1GHz and DDR3 1066 MT/s support Lokesh Vutla
2017-12-20 16:05   ` Tom Rini
2017-12-21  4:46     ` Lokesh Vutla
2017-12-20 15:29 ` [U-Boot] [PATCH v2 3/5] tools: omapimage: Fix mismatch of image size in header Lokesh Vutla
2017-12-20 15:29 ` [U-Boot] [PATCH v2 4/5] arm: am33xx: Avoid writing into reserved DPLL divider Lokesh Vutla
2017-12-20 15:29 ` Lokesh Vutla [this message]

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=20171220152940.27950-6-lokeshvutla@ti.com \
    --to=lokeshvutla@ti.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.