Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: HDMI Repoll after pm?
Date: Thu, 10 Dec 2015 10:53:32 +0100	[thread overview]
Message-ID: <s5htwnq7hpf.wl-tiwai@suse.de> (raw)
In-Reply-To: <56694A4F.8070104@canonical.com>

On Thu, 10 Dec 2015 10:47:59 +0100,
David Henningsson wrote:
> 
> Hi Takashi,
> 
> A recent change in sound.git seems to have introduced some repoll after 
> pm. Is this an intentional change? I don't think it's wrong per se (it 
> stops after 6 repolls), but it breaks my hda-emu tester when "list" does 
> not return the expected input.

Hm, there is no such an intended change.

> To reproduce, try running:
> 
> ./hda-emu 
> codecs/canonical/92hd91bxx-dell-inspiron-5423-ccert-201208-11456 -i 1
>  > pm
> .... lots of data ....
> ** TEST_PM DONE **
> HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0
> JACK report HDMI/DP, status 0
>  > list
> 1: HDMI/DP Jack:0 (1)
> 2: IEC958 Playback Con Mask:0 (1)
> 3: IEC958 Playback Pro Mask:0 (1)
> 4: IEC958 Playback Default:0 (1)
> 5: IEC958 Playback Switch:0 (1)
> 6: ELD:0 (1)
> 7: Playback Channel Map:0 (1)
> HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0
> JACK report HDMI/DP, status 0
>  >
> 
> ...notice how the last two lines are somewhat unexpected output for a 
> "list" command, but I can make my tool more robust in case you confirm 
> this is an expected change.

When the list may trigger some runtime PM, the jack status report
itself should have been present at resume in earlier version, too.
Do you see the repoll there?


Takashi

  reply	other threads:[~2015-12-10  9:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10  9:47 HDMI Repoll after pm? David Henningsson
2015-12-10  9:53 ` Takashi Iwai [this message]
2015-12-10 12:59   ` David Henningsson
2015-12-10 13:18     ` Takashi Iwai
2015-12-10 13:28       ` David Henningsson
2015-12-10 13:38         ` Takashi Iwai

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=s5htwnq7hpf.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.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