From: Peter Ujfalusi <peter.ujfalusi@ti.com> To: Tony Lindgren <tony@atomide.com> Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 1/2] ARM: OMAP: board-4430sdp: MUX configuration for sys_nirq2 Date: Fri, 06 Jul 2012 14:59:29 +0200 [thread overview] Message-ID: <4FF6E131.1030008@ti.com> (raw) In-Reply-To: <1341564590-14024-1-git-send-email-peter.ujfalusi@ti.com> Hi, On 07/06/2012 10:49 AM, Peter Ujfalusi wrote: > The sys_nirq2 is used for twl6040, make sure the pin is configured > correctly. Please ignore this two patch, I'll resend them with the correct MUX config. By mistake I have set MUX_MODE1, while it must be set MUX_MODE0. It was working with MUX_MODE1, but it is not aligned with the TRM... Sorry, Péter > > Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com> > --- > arch/arm/mach-omap2/board-4430sdp.c | 3 +++ > 1 files changed, 3 insertions(+), 0 deletions(-) > > diff --git a/arch/arm/mach-omap2/board-4430sdp.c b/arch/arm/mach-omap2/board-4430sdp.c > index c4e17641..050cc8e 100644 > --- a/arch/arm/mach-omap2/board-4430sdp.c > +++ b/arch/arm/mach-omap2/board-4430sdp.c > @@ -827,6 +827,9 @@ static void __init omap_4430sdp_display_init(void) > #ifdef CONFIG_OMAP_MUX > static struct omap_board_mux board_mux[] __initdata = { > OMAP4_MUX(USBB2_ULPITLL_CLK, OMAP_MUX_MODE4 | OMAP_PIN_OUTPUT), > + /* NIRQ2 for twl6040 */ > + OMAP4_MUX(SYS_NIRQ2, OMAP_MUX_MODE1 | > + OMAP_PIN_INPUT_PULLUP | OMAP_PIN_OFF_WAKEUPENABLE), > { .reg_offset = OMAP_MUX_TERMINATOR }, > }; > > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: peter.ujfalusi@ti.com (Peter Ujfalusi) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/2] ARM: OMAP: board-4430sdp: MUX configuration for sys_nirq2 Date: Fri, 06 Jul 2012 14:59:29 +0200 [thread overview] Message-ID: <4FF6E131.1030008@ti.com> (raw) In-Reply-To: <1341564590-14024-1-git-send-email-peter.ujfalusi@ti.com> Hi, On 07/06/2012 10:49 AM, Peter Ujfalusi wrote: > The sys_nirq2 is used for twl6040, make sure the pin is configured > correctly. Please ignore this two patch, I'll resend them with the correct MUX config. By mistake I have set MUX_MODE1, while it must be set MUX_MODE0. It was working with MUX_MODE1, but it is not aligned with the TRM... Sorry, P?ter > > Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com> > --- > arch/arm/mach-omap2/board-4430sdp.c | 3 +++ > 1 files changed, 3 insertions(+), 0 deletions(-) > > diff --git a/arch/arm/mach-omap2/board-4430sdp.c b/arch/arm/mach-omap2/board-4430sdp.c > index c4e17641..050cc8e 100644 > --- a/arch/arm/mach-omap2/board-4430sdp.c > +++ b/arch/arm/mach-omap2/board-4430sdp.c > @@ -827,6 +827,9 @@ static void __init omap_4430sdp_display_init(void) > #ifdef CONFIG_OMAP_MUX > static struct omap_board_mux board_mux[] __initdata = { > OMAP4_MUX(USBB2_ULPITLL_CLK, OMAP_MUX_MODE4 | OMAP_PIN_OUTPUT), > + /* NIRQ2 for twl6040 */ > + OMAP4_MUX(SYS_NIRQ2, OMAP_MUX_MODE1 | > + OMAP_PIN_INPUT_PULLUP | OMAP_PIN_OFF_WAKEUPENABLE), > { .reg_offset = OMAP_MUX_TERMINATOR }, > }; > >
next prev parent reply other threads:[~2012-07-06 12:59 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-06 8:49 [PATCH 1/2] ARM: OMAP: board-4430sdp: MUX configuration for sys_nirq2 Peter Ujfalusi 2012-07-06 8:49 ` Peter Ujfalusi 2012-07-06 8:49 ` [PATCH 2/2] ARM: OMAP: board-omap4panda: " Peter Ujfalusi 2012-07-06 8:49 ` Peter Ujfalusi 2012-07-06 9:03 ` Shilimkar, Santosh 2012-07-06 9:03 ` Shilimkar, Santosh 2012-07-06 9:02 ` [PATCH 1/2] ARM: OMAP: board-4430sdp: " Shilimkar, Santosh 2012-07-06 9:02 ` Shilimkar, Santosh 2012-07-06 9:22 ` Peter Ujfalusi 2012-07-06 9:22 ` Peter Ujfalusi 2012-07-06 9:24 ` Shilimkar, Santosh 2012-07-06 9:24 ` Shilimkar, Santosh 2012-07-06 12:59 ` Peter Ujfalusi [this message] 2012-07-06 12:59 ` Peter Ujfalusi
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=4FF6E131.1030008@ti.com \ --to=peter.ujfalusi@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=tony@atomide.com \ /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: linkBe 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.