All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "Neri, Ricardo" <ricardo.neri@ti.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 4/6] ASoC: OMAP: Add CPU DAI driver for HDMI
Date: Sun, 8 May 2011 12:14:04 +0100	[thread overview]
Message-ID: <4DC67AFC.5040607@ti.com> (raw)
In-Reply-To: <20110508103402.GA12921@opensource.wolfsonmicro.com>

On 08/05/11 11:34, Mark Brown wrote:
> On Sat, May 07, 2011 at 07:05:17PM -0500, Ricardo Neri wrote:
>> Am Freitag, den 06.05.2011, 08:21 -0500 schrieb Mark Brown:
> 
>>> Why do you need to check at all?  The playback won't work when the
>>> output isn't connected but the application layer will find that out when
>>> there's no data transfer anyway.  If you implement the check in startup
>>> I'd imagine there may be some races with hotplug of HDMI cables.
> 
>> I need to check somewhere if the Display Subsystem (and the HDMI IP) is
>> on. Otherwise I will have L3 interconnect errors when trying to access
>> the DSS while it is power-disconnected. I need the HDMI IP on for
>> getting configurations (e.g, deep color mode) and use the HDMI audio
>> FIFO.
> 
> I repeat my question - why do you need to check this?  You'll get errors
> but you're generating an error anyway so it's not clear what the urgency
> is.
> 

I think the problem here is that the errors are fatal data aborts here when L3 DSS access is disabled.

Liam

  reply	other threads:[~2011-05-08 11:14 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05  7:21 [PATCH 0/6] ASoC: OMAP4: Add support for HDMI audio Ricardo Neri
2011-05-05  7:21 ` [PATCH 1/6] OMAP4: HDMI: Add OMAP device for HDMI audio CPU DAI Ricardo Neri
2011-05-05  8:17   ` Mark Brown
2011-05-05 19:24     ` Ricardo Neri
2011-05-06 13:16       ` Mark Brown
2011-05-08  0:09         ` Ricardo Neri
2011-05-05  7:21 ` [PATCH 2/6] OMAP4: Add device for HDMI OMAP4 audio for ASoC machine driver Ricardo Neri
2011-05-05  8:18   ` Mark Brown
2011-05-05 19:26     ` Ricardo Neri
2011-05-05  7:21 ` [PATCH 3/6] ASoC: OMAP: Add header for HDMI CPU DAI Ricardo Neri
2011-05-05  8:25   ` Mark Brown
2011-05-05 21:10     ` Ricardo Neri
2011-05-05  7:21 ` [PATCH 4/6] ASoC: OMAP: Add CPU DAI driver for HDMI Ricardo Neri
2011-05-05  8:22   ` Mark Brown
2011-05-05 19:35     ` Ricardo Neri
2011-05-06 13:21       ` Mark Brown
2011-05-08  0:05         ` Ricardo Neri
2011-05-08 10:34           ` Mark Brown
2011-05-08 11:14             ` Liam Girdwood [this message]
2011-05-08 15:56               ` Mark Brown
2011-05-08 19:44                 ` Liam Girdwood
2011-05-08 23:41                   ` Mark Brown
2011-05-12 13:48                     ` Neri, Ricardo
2011-05-05  7:21 ` [PATCH 5/6] ASoC: OMAP4: Add HDMI Audio machine driver for OMAP4 boards Ricardo Neri
2011-05-05  8:25   ` Mark Brown
2011-05-05 21:09     ` Ricardo Neri
2011-05-06 13:22       ` Mark Brown
2011-05-05  7:21 ` [PATCH 6/6] ASoC: OMAP: Update Makefile and Kconfig for HDMI audio Ricardo Neri

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=4DC67AFC.5040607@ti.com \
    --to=lrg@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=ricardo.neri@ti.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.