All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Lu, Brent" <brent.lu@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"Takashi Iwai" <tiwai@suse.com>,
	"Kai Vehmanen" <kai.vehmanen@linux.intel.com>,
	"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
	"Mohan Kumar" <mkumard@nvidia.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Zhi, Yong" <yong.zhi@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA: hda/hdmi: run eld notify in delay work
Date: Wed, 05 Oct 2022 11:45:37 +0200	[thread overview]
Message-ID: <87ilkyvc1q.wl-tiwai@suse.de> (raw)
In-Reply-To: <CY5PR11MB62571E282C37DDFBD4058D99975D9@CY5PR11MB6257.namprd11.prod.outlook.com>

On Wed, 05 Oct 2022 10:14:19 +0200,
Lu, Brent wrote:
> 
> > 
> > ... and on the further consideration, I believe the best solution is to just get rid of
> > the whole check.
> > 
> > It was introduced by the commit eb399d3c99d8 along with the 8ae743e82f0b
> > that checks the suspend state.  The latter is still meaningful (we should skip the
> > bogus notification at suspend).
> > However, the former -- the code path we're dealing with -- doesn't help much in
> > the recent code.  That fix was required because the driver probed the ELD bits
> > via HD-audio verb at the time of the fix commit; that is, the driver had to wake
> > up the codec for updating the ELD.  OTOH, now ELD is read directly from the
> > graphics chip without the codec wakeup.  So the skip makes little sense.
> Hi Takashi,
> 
> I've got the test result from ODM which is positive. During 60 test runs, the elf notify
> running in suspend happened 10 times and the audio is normal. The patch is looking
> good.

Thanks for confirmation.  The fix will be included in 6.1-rc1.


Takashi

WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: "Lu, Brent" <brent.lu@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Kai Vehmanen" <kai.vehmanen@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
	"Takashi Iwai" <tiwai@suse.com>,
	"Mohan Kumar" <mkumard@nvidia.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Zhi, Yong" <yong.zhi@intel.com>
Subject: Re: [PATCH] ALSA: hda/hdmi: run eld notify in delay work
Date: Wed, 05 Oct 2022 11:45:37 +0200	[thread overview]
Message-ID: <87ilkyvc1q.wl-tiwai@suse.de> (raw)
In-Reply-To: <CY5PR11MB62571E282C37DDFBD4058D99975D9@CY5PR11MB6257.namprd11.prod.outlook.com>

On Wed, 05 Oct 2022 10:14:19 +0200,
Lu, Brent wrote:
> 
> > 
> > ... and on the further consideration, I believe the best solution is to just get rid of
> > the whole check.
> > 
> > It was introduced by the commit eb399d3c99d8 along with the 8ae743e82f0b
> > that checks the suspend state.  The latter is still meaningful (we should skip the
> > bogus notification at suspend).
> > However, the former -- the code path we're dealing with -- doesn't help much in
> > the recent code.  That fix was required because the driver probed the ELD bits
> > via HD-audio verb at the time of the fix commit; that is, the driver had to wake
> > up the codec for updating the ELD.  OTOH, now ELD is read directly from the
> > graphics chip without the codec wakeup.  So the skip makes little sense.
> Hi Takashi,
> 
> I've got the test result from ODM which is positive. During 60 test runs, the elf notify
> running in suspend happened 10 times and the audio is normal. The patch is looking
> good.

Thanks for confirmation.  The fix will be included in 6.1-rc1.


Takashi

  reply	other threads:[~2022-10-05  9:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 13:58 [PATCH] ALSA: hda/hdmi: run eld notify in delay work Brent Lu
2022-09-27 13:58 ` Brent Lu
2022-09-27 14:11 ` Takashi Iwai
2022-09-27 14:11   ` Takashi Iwai
2022-09-28  2:06   ` Lu, Brent
2022-09-28  2:06     ` Lu, Brent
2022-09-28  7:14     ` Takashi Iwai
2022-09-28  7:14       ` Takashi Iwai
2022-09-28  8:09       ` Takashi Iwai
2022-09-28  8:09         ` Takashi Iwai
2022-09-28  8:37         ` Takashi Iwai
2022-09-28  8:37           ` Takashi Iwai
2022-10-05  8:14           ` Lu, Brent
2022-10-05  8:14             ` Lu, Brent
2022-10-05  9:45             ` Takashi Iwai [this message]
2022-10-05  9:45               ` 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=87ilkyvc1q.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=brent.lu@intel.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkumard@nvidia.com \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.com \
    --cc=ville.syrjala@linux.intel.com \
    --cc=yong.zhi@intel.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.