All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxim Mikityanskiy <maxtram95@gmail.com>
To: Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>
Cc: Bard Liao <yung-chuan.liao@linux.intel.com>,
	Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	WangYuli <wangyuli@uniontech.com>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	Maxim Mikityanskiy <maxtram95@gmail.com>
Subject: [PATCH v2 0/2] Fix Optimus when GPU has no sound
Date: Sat,  8 Feb 2025 23:46:00 +0200	[thread overview]
Message-ID: <20250208214602.39607-1-maxtram95@gmail.com> (raw)

See the commit descriptions.

As agreed in the previous discussion [1], this series adds the
non-functional NVIDIA HDA controller on Lenovo IdeaPad Z570 to the
denylist, and includes the runtime PM workaround from v1, which now
prints a warning to dmesg asking the user to add the device to the
denylist if it's affected and not already there.

[1]: https://lore.kernel.org/linux-sound/877catiffo.wl-tiwai@suse.de/

Maxim Mikityanskiy (2):
  ALSA: hda: intel: Fix Optimus when GPU has no sound
  ALSA: hda: intel: Add Lenovo IdeaPad Z570 to probe denylist

 sound/pci/hda/hda_intel.c | 44 ++++++++++++++++++++++++++++++++++++++-
 1 file changed, 43 insertions(+), 1 deletion(-)

-- 
2.43.0


             reply	other threads:[~2025-02-08 21:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-08 21:46 Maxim Mikityanskiy [this message]
2025-02-08 21:46 ` [PATCH v2 1/2] ALSA: hda: intel: Fix Optimus when GPU has no sound Maxim Mikityanskiy
2025-02-08 21:46 ` [PATCH v2 2/2] ALSA: hda: intel: Add Lenovo IdeaPad Z570 to probe denylist Maxim Mikityanskiy
2025-02-10  8:46 ` [PATCH v2 0/2] Fix Optimus when GPU has no sound 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=20250208214602.39607-1-maxtram95@gmail.com \
    --to=maxtram95@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=tiwai@suse.com \
    --cc=wangyuli@uniontech.com \
    --cc=yung-chuan.liao@linux.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.