Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: "David Härdeman" <david@hardeman.nu>
Cc: "alsa-user@lists.sourceforge.net"
	<alsa-user@lists.sourceforge.net>,
	alsa-devel@alsa-project.org
Subject: Re: [Intel-gfx] Problems with HDMI audio on Intel DG45FC	motherboard
Date: Thu, 5 Nov 2009 17:22:09 +0800	[thread overview]
Message-ID: <20091105092209.GA23782@localhost> (raw)
In-Reply-To: <b3e8c2bfd1e1ff82a1e68a4e03950238.squirrel@www.hardeman.nu>

On Thu, Nov 05, 2009 at 05:06:22PM +0800, David Härdeman wrote:
> On Thu, November 5, 2009 08:47, Wu Fengguang wrote:
> > On Thu, Nov 05, 2009 at 08:46:55AM +0800, David wrote:
> >> Currently doing some testing with sticky stream id and format.
> >>
> >> Could you test the attached patch (applies to alsa git repo, without
> >> your patchset) and see if you get the initial 0.5s silence with your
> >> receiver?
> >
> > Yes it worked!
> 
> Worked as in you get no 0.5s of initial silence? Or worked as in you at
> least got some audio and the computer didn't crash? :)

no 0.5s :)

> > However something is broken when
> >
> > CONFIG_SND_HDA_POWER_SAVE=y
> > CONFIG_SND_HDA_POWER_SAVE_DEFAULT=1

In the above config, you need to restart playback within 1s to avoid
losing the first 0.5s samples. (Otherwise power save will kick in.)

> I was kind of expecting my patch to break both power save and
> suspend/resume given that it expects the stream format and id to survive
> from pcm_close to pcm_prepare (which they probably won't if power saving

Don't worry, I fixed that in my implementation :)

> and/or resume/suspend kicks in). Power save also seems to mess up some
> other parts of the driver even without my patch (haven't really looked
> into that yet...power save might be tricky with HDMI from what I've seen
> so far).

Yes, HDMI power save is inherently not possible given that the sink
devices have the more than 1s delays..

> The patch was just a test case to see if it was enough to fix the 0.5s
> silence on receivers which are less picky than mine (it still doesn't fix
> the 0.5s silence on my receiver but it fixes the
> silence-for-the-duration-of-a-track problem).
> 
> Next up, more testing with VCFG when I have more time. I have actually
> tried setting that bit but it didn't change anything. Comments in
> setup_dig_out_stream from hda_codec.c seems to suggest that it's a bit
> more complex than just setting the right bit.

No worry, I guess that's realtek specific problem (spdif_status_reset
is only set by it).

> > Attached is my updated patchset, which includes the sticky
> > stream/infoframe features.
> 
> Thanks, I'll take a look at it as soon as possible.

Thanks,
Fengguang
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2009-11-05  9:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091011214513.GB12771@hardeman.nu>
     [not found] ` <20091014015455.GI13364@zhen-devel.sh.intel.com>
     [not found]   ` <20091014020044.GA10032@localhost>
     [not found]     ` <20091014174053.GA31149@hardeman.nu>
2009-10-20  1:26       ` [Intel-gfx] Problems with HDMI audio on Intel DG45FC motherboard Wu Fengguang
2009-10-20 22:37         ` David Härdeman
2009-10-21  1:38           ` Wu Fengguang
2009-10-25 22:31             ` David Härdeman
2009-10-27  8:57               ` Wu Fengguang
2009-11-08 10:41             ` Takashi Iwai
2009-10-20 22:43         ` Shane W
2009-10-26 23:11           ` David Härdeman
2009-10-27  9:08             ` Wu Fengguang
2009-10-27  3:28           ` Wu Fengguang
     [not found]           ` <2da93e57183a480510f5b67c24ba11d0.squirrel@www.hardeman.nu>
     [not found]             ` <20091028044621.GA18453@localhost>
     [not found]               ` <0323437dc2fc33a33ec9285505a36434.squirrel@www.hardeman.nu>
     [not found]                 ` <20091029094602.GA3589@localhost>
     [not found]                   ` <20091029222932.GA1109@hardeman.nu>
2009-11-02  9:11                     ` Wu Fengguang
     [not found]                       ` <20091105004655.GA25580@hardeman.nu>
     [not found]                         ` <20091105074731.GB3016@localhost>
     [not found]                           ` <b3e8c2bfd1e1ff82a1e68a4e03950238.squirrel@www.hardeman.nu>
2009-11-05  9:22                             ` Wu Fengguang [this message]
     [not found]                               ` <5a703067d8395f3f80e4fb6a5227d117.squirrel@www.hardeman.nu>
2009-11-11  7:05                                 ` Wu Fengguang
2009-11-12  9:49                                   ` Paul Fertser

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=20091105092209.GA23782@localhost \
    --to=fengguang.wu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=david@hardeman.nu \
    /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