From: Kevin Hilman <khilman@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [PATCH v2 1/2] ARM: OMAP: board-4430sdp: MUX configuration for sys_nirq2
Date: Fri, 06 Jul 2012 07:16:25 -0700 [thread overview]
Message-ID: <874nplc6va.fsf@ti.com> (raw)
In-Reply-To: <1341580752-5501-2-git-send-email-peter.ujfalusi@ti.com> (Peter Ujfalusi's message of "Fri, 6 Jul 2012 15:19:11 +0200")
Peter Ujfalusi <peter.ujfalusi@ti.com> writes:
> The sys_nirq2 is used for twl6040, make sure the pin is configured
> correctly.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> Acked-by: Santosh Shilimkar <santosh.shilimkar@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..72cd206 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_MODE0 |
> + OMAP_PIN_INPUT_PULLUP | OMAP_PIN_OFF_WAKEUPENABLE),
Since this is TWL6030 specific, it should rather be done in TWL code
like I did for sys_nirq1:
http://marc.info/?l=linux-omap&m=134090312118873&w=2
That would avoid having to do this in both board files.
I thought about adding sys_nirq2 in my patch too, but did not know how
to properly test it.
Kevin
> { .reg_offset = OMAP_MUX_TERMINATOR },
> };
next prev parent reply other threads:[~2012-07-06 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 13:19 [PATCH v2 0/2] ARM: OMAP4 SDP/PandaBoard: Fix sys_nirq2 mux configuration Peter Ujfalusi
2012-07-06 13:19 ` [PATCH v2 1/2] ARM: OMAP: board-4430sdp: MUX configuration for sys_nirq2 Peter Ujfalusi
2012-07-06 14:16 ` Kevin Hilman [this message]
2012-07-06 14:33 ` Shilimkar, Santosh
2012-07-09 9:38 ` Peter Ujfalusi
2012-07-09 12:14 ` Tony Lindgren
2012-07-09 16:41 ` Kevin Hilman
2012-07-06 13:19 ` [PATCH v2 2/2] ARM: OMAP: board-omap4panda: " 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=874nplc6va.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=santosh.shilimkar@ti.com \
--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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).