All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: HDMI Repoll after pm?
Date: Thu, 10 Dec 2015 13:59:59 +0100	[thread overview]
Message-ID: <5669774F.3060709@canonical.com> (raw)
In-Reply-To: <s5htwnq7hpf.wl-tiwai@suse.de>



On 2015-12-10 10:53, Takashi Iwai wrote:
> 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.

After testing some more, I've found that reverting e90247f9 (Split ELD 
update code from hdmi_present_sense) fixes the issue, so it seems like 
this commit indeed contains a functional change...

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

To clarify, it's not power up or power down, it's flush_delayed_work 
that runs after every hda-emu command that causes "list" to also report 
the jack status.


-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

  reply	other threads:[~2015-12-10 12:59 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
2015-12-10 12:59   ` David Henningsson [this message]
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=5669774F.3060709@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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.