From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: Kevin Hilman <khilman@ti.com>, Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] ARM: OMAP: board-4430sdp: MUX configuration for sys_nirq2
Date: Mon, 09 Jul 2012 11:38:55 +0200 [thread overview]
Message-ID: <4FFAA6AF.2010004@ti.com> (raw)
In-Reply-To: <CAMQu2gx4927Ze9tRUFq9QPubGFWfK9bHqZhVCb7c39O=WeWA3Q@mail.gmail.com>
On 07/06/2012 04:33 PM, Shilimkar, Santosh wrote:
>> 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.
>>
> Though the pin is TWL specific, it need not be same on
> different board with different SOCs. Especially when you need to
> set MUX mode etc. So doing from board file is still better
> since TWL6030/40 can be connected to non OMAP4 devices
> where the muxing can be different.
>
> With current know boards with TWL6030/40, this is not
> a strong requirement though.
There can be board which has twl6030 but does not have twl6040.
The twl6040 is the recommended audio solution for OMAP4+ systems but it can be
replaced by other codec on some boards.
This is the reason I have put the mux configuration into the board files for
sys_nirq2 (which is in these cases are used to handle the interrupt from twl6040).
--
Péter
--
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 v2 1/2] ARM: OMAP: board-4430sdp: MUX configuration for sys_nirq2
Date: Mon, 09 Jul 2012 11:38:55 +0200 [thread overview]
Message-ID: <4FFAA6AF.2010004@ti.com> (raw)
In-Reply-To: <CAMQu2gx4927Ze9tRUFq9QPubGFWfK9bHqZhVCb7c39O=WeWA3Q@mail.gmail.com>
On 07/06/2012 04:33 PM, Shilimkar, Santosh wrote:
>> 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.
>>
> Though the pin is TWL specific, it need not be same on
> different board with different SOCs. Especially when you need to
> set MUX mode etc. So doing from board file is still better
> since TWL6030/40 can be connected to non OMAP4 devices
> where the muxing can be different.
>
> With current know boards with TWL6030/40, this is not
> a strong requirement though.
There can be board which has twl6030 but does not have twl6040.
The twl6040 is the recommended audio solution for OMAP4+ systems but it can be
replaced by other codec on some boards.
This is the reason I have put the mux configuration into the board files for
sys_nirq2 (which is in these cases are used to handle the interrupt from twl6040).
--
P?ter
next prev parent reply other threads:[~2012-07-09 9:38 UTC|newest]
Thread overview: 16+ 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 ` 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 13:19 ` Peter Ujfalusi
2012-07-06 14:16 ` Kevin Hilman
2012-07-06 14:16 ` Kevin Hilman
2012-07-06 14:33 ` Shilimkar, Santosh
2012-07-06 14:33 ` Shilimkar, Santosh
2012-07-09 9:38 ` Peter Ujfalusi [this message]
2012-07-09 9:38 ` Peter Ujfalusi
2012-07-09 12:14 ` Tony Lindgren
2012-07-09 12:14 ` Tony Lindgren
2012-07-09 16:41 ` Kevin Hilman
2012-07-09 16:41 ` Kevin Hilman
2012-07-06 13:19 ` [PATCH v2 2/2] ARM: OMAP: board-omap4panda: " Peter Ujfalusi
2012-07-06 13:19 ` 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=4FFAA6AF.2010004@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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 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.