All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Allen Ballway <ballway@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Brady Norander" <bradynorander@gmail.com>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"Takashi Iwai" <tiwai@suse.com>,
	"Ranjani Sridharan" <ranjani.sridharan@linux.intel.com>,
	"Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
	"Mark Brown" <broonie@kernel.org>,
	linux-sound@vger.kernel.org,
	"Mark Hasemeyer" <markhas@chromium.org>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Cezary Rojewski" <cezary.rojewski@intel.com>
Subject: Re: [PATCH] ALSA: hda: intel-dsp-config: Fix Azulle Access 4 quirk detection
Date: Mon, 6 May 2024 13:02:31 -0500	[thread overview]
Message-ID: <b2375610-4044-49e6-86e9-5c172abb2ffa@linux.intel.com> (raw)
In-Reply-To: <CAEs41JC-vJaMHj6fzmNO=-bu5oURRA-u565sN2=yzBeVtKb=4g@mail.gmail.com>




> Unfortunately the above patch didn't fix the issue, nor did I see any
> of the change logs in dmesg.
> Are there other alternative solutions or information I could gather to
> make a more general solution?

File an issue here: https://github.com/thesofproject/linux/issues

and attach the NHLT table:

sudo cat /sys/firmware/acpi/tables/NHLT > nhtl.dat; gzip nhlt.dat

as well as the results of alsa-info.

  reply	other threads:[~2024-05-06 18:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30 21:28 [PATCH] ALSA: hda: intel-dsp-config: Fix Azulle Access 4 quirk detection Allen Ballway
2024-04-30 21:46 ` Pierre-Louis Bossart
2024-05-06 16:39   ` Allen Ballway
2024-05-06 18:02     ` Pierre-Louis Bossart [this message]
2024-06-20 19:27       ` Allen Ballway
2024-06-21  6:15         ` Amadeusz Sławiński
2024-06-21  8:35           ` Pierre-Louis Bossart
2024-06-25 21:37             ` Guenter Roeck
2024-06-26  7:04               ` Pierre-Louis Bossart
2024-06-26 13:09                 ` Guenter Roeck
2024-06-26 13:30                   ` Pierre-Louis Bossart
2024-06-26 13:37                   ` Takashi Iwai
2024-06-26 14:09                     ` Guenter Roeck

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=b2375610-4044-49e6-86e9-5c172abb2ffa@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=ballway@chromium.org \
    --cc=bradynorander@gmail.com \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=markhas@chromium.org \
    --cc=perex@perex.cz \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=tiwai@suse.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.