From: Takashi Iwai <tiwai@suse.de>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] hda - delayed ELD repoll
Date: Tue, 22 Nov 2011 08:30:24 +0100 [thread overview]
Message-ID: <s5hr510397z.wl%tiwai@suse.de> (raw)
In-Reply-To: <20111121064811.GA24027@localhost>
At Mon, 21 Nov 2011 14:48:11 +0800,
Wu Fengguang wrote:
>
> On Wed, Nov 16, 2011 at 04:29:47PM +0800, Wu, Fengguang wrote:
> > The Intel HDMI chips (ironlake at least) are found to have ~250ms delay
> > between the ELD_Valid=1 hotplug event is send and the ELD buffer becomes
> > actually readable. During the time the ELD buffer is mysteriously all 0.
> >
> > Fix it by scheduling a delayed work to re-read ELD buffer after 300ms.
>
> Just FYI.
>
> Up to now the 300ms looks sufficient. But if ever there comes longer
> delays, I've already prepared a patch for retrying it for several times ;)
Thanks. I think it's safer to have a repoll mechanism.
But, looking at the patch, one question remains:
> @@ -989,10 +990,9 @@ static void hdmi_present_sense(struct hd
> if (eld_valid) {
> if (!snd_hdmi_get_eld(eld, codec, pin_nid))
> snd_hdmi_show_eld(eld);
> - else if (retry) {
> + else if (repoll) {
> queue_delayed_work(codec->bus->workq,
> - &per_pin->work,
> - msecs_to_jiffies(300));
> + &per_pin->work, repoll * HZ / 3);
Do you really want to wait longer with a higher repoll number?
Takashi
next prev parent reply other threads:[~2011-11-22 7:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 8:29 [PATCH 0/3] ELD fixes for 3.2 Wu Fengguang
2011-11-16 8:29 ` [PATCH 1/3] hda - fix ELD memory leak Wu Fengguang
2011-11-16 8:29 ` [PATCH 2/3] hda - delayed ELD repoll Wu Fengguang
2011-11-21 6:48 ` Wu Fengguang
2011-11-22 7:30 ` Takashi Iwai [this message]
2011-11-22 8:00 ` Wu Fengguang
2011-11-16 8:29 ` [PATCH 3/3] hda - move eld->spk_alloc fixup to hdmi_update_eld() Wu Fengguang
2011-11-16 9:54 ` [PATCH 0/3] ELD fixes for 3.2 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=s5hr510397z.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome