All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shilimkar, Santosh" <santosh.shilimkar@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,
	Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Re: [PATCH 1/2] ARM: OMAP: board-4430sdp: MUX configuration for sys_nirq2
Date: Fri, 6 Jul 2012 14:54:49 +0530	[thread overview]
Message-ID: <CAMQu2gw9ccxk3KL8KUVxnLX8nTsDMSWyokHVMqR8Feo6DyrNWA@mail.gmail.com> (raw)
In-Reply-To: <4FF6AE6F.4000808@ti.com>

+ Russell

On Fri, Jul 6, 2012 at 2:52 PM, Peter Ujfalusi <peter.ujfalusi@ti.com> wrote:
> On 07/06/2012 11:02 AM, Shilimkar, Santosh wrote:
>> On Fri, Jul 6, 2012 at 2:19 PM, Peter Ujfalusi <peter.ujfalusi@ti.com> wrote:
>>> The sys_nirq2 is used for twl6040, make sure the pin is configured
>>> correctly.
>>>
>>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>>> ---
>> Should remove the boot-loader pin-muxing dependency.
>> Was this the reason, Audio had some issues on OMAP4430
>> SDP as reported by Russell ?
>
> The boot loader never configured the sys_nirq2, I have sent a patch for u-boot
> to do this, but it is said that the kernel should take care of this.
>
> We did not had jack detection working with upstream u-boot, kernel (I have
> patched u-boot so I have not seen this issue).
> Now if the board is booted without HS connected, upon connecting the HS we
> will recognize it and it should be all fine.
> So yes this was the reason why Russell had issues with audio.
>
Thanks Peter for tracking it down.

Regards
santosh

WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Shilimkar, Santosh)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: OMAP: board-4430sdp: MUX configuration for sys_nirq2
Date: Fri, 6 Jul 2012 14:54:49 +0530	[thread overview]
Message-ID: <CAMQu2gw9ccxk3KL8KUVxnLX8nTsDMSWyokHVMqR8Feo6DyrNWA@mail.gmail.com> (raw)
In-Reply-To: <4FF6AE6F.4000808@ti.com>

+ Russell

On Fri, Jul 6, 2012 at 2:52 PM, Peter Ujfalusi <peter.ujfalusi@ti.com> wrote:
> On 07/06/2012 11:02 AM, Shilimkar, Santosh wrote:
>> On Fri, Jul 6, 2012 at 2:19 PM, Peter Ujfalusi <peter.ujfalusi@ti.com> wrote:
>>> The sys_nirq2 is used for twl6040, make sure the pin is configured
>>> correctly.
>>>
>>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>>> ---
>> Should remove the boot-loader pin-muxing dependency.
>> Was this the reason, Audio had some issues on OMAP4430
>> SDP as reported by Russell ?
>
> The boot loader never configured the sys_nirq2, I have sent a patch for u-boot
> to do this, but it is said that the kernel should take care of this.
>
> We did not had jack detection working with upstream u-boot, kernel (I have
> patched u-boot so I have not seen this issue).
> Now if the board is booted without HS connected, upon connecting the HS we
> will recognize it and it should be all fine.
> So yes this was the reason why Russell had issues with audio.
>
Thanks Peter for tracking it down.

Regards
santosh

  reply	other threads:[~2012-07-06  9:25 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 [this message]
2012-07-06  9:24       ` Shilimkar, Santosh
2012-07-06 12:59 ` Peter Ujfalusi
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=CAMQu2gw9ccxk3KL8KUVxnLX8nTsDMSWyokHVMqR8Feo6DyrNWA@mail.gmail.com \
    --to=santosh.shilimkar@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=peter.ujfalusi@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.