linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Tony Lindgren <tony@atomide.com>,
	Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
Cc: linux-omap@vger.kernel.org
Subject: Re: [pandaboard] audio initialization fails due to TWL6040
Date: Mon, 30 Dec 2013 09:35:02 +0200	[thread overview]
Message-ID: <52C12226.6010404@ti.com> (raw)
In-Reply-To: <20131205185349.GH26766@atomide.com>

Hi Tony,

I have missed this mail...

On 12/05/2013 08:53 PM, Tony Lindgren wrote:
> * Tobias Jakobi <tjakobi@math.uni-bielefeld.de> [131203 14:45]:
>> And another one!
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=66451
> 
> Maybe Peter can take a look at this one?

It has been already fixed (bug in the arch/arm/mm/dma-mapping.c)

> FYI, Peter, only slightly related to this, but can you also please
> unravel the mcbsp and sidetone .dtsi entries to be separate
> devices? I'm hoping to deprecate ti,hwmods for v3.15 and use
> the compatible property instead, so we need to have 1-to-1
> mapping of devices defined in the .dtsi files compared to the
> real hardware devices mapped in the omap_hwmod_*_data.c files.
> 
> There's some more info regarding that in thread:
> 
> http://www.spinics.net/lists/arm-kernel/msg288036.html

How urgent this is?
Due to a 'hw feature' around the sidetone this is not as straight forward as
it sounds...
I can put this to my to do list.

-- 
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

  reply	other threads:[~2013-12-30  7:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 22:44 [pandaboard] audio initialization fails due to TWL6040 Tobias Jakobi
2013-12-05 18:53 ` Tony Lindgren
2013-12-30  7:35   ` Peter Ujfalusi [this message]
2014-01-07 22:53     ` Tony Lindgren
2014-01-08 13:23       ` Peter Ujfalusi
2014-01-08 16:49         ` Tony Lindgren

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=52C12226.6010404@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tjakobi@math.uni-bielefeld.de \
    --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).