From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Cezary Rojewski <cezary.rojewski@intel.com>,
Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org, tiwai@suse.com
Subject: Re: [PATCH] ALSA: hda: Refactor Intel NHLT init
Date: Thu, 23 Apr 2020 11:29:38 -0500 [thread overview]
Message-ID: <8e3d7780-d776-d964-d8a8-4618b7ae045a@linux.intel.com> (raw)
In-Reply-To: <b37cb05b-f4c2-e747-c3f0-1582ed3afadd@intel.com>
On 4/23/20 6:40 AM, Cezary Rojewski wrote:
> On 2020-04-23 13:24, Takashi Iwai wrote:
>> On Thu, 23 Apr 2020 13:21:36 +0200,
>> Cezary Rojewski wrote:
>>>
>>> NHLT fetch based on _DSM prevents ACPI table override mechanism from
>>> being utilized. Make use of acpi_get_table to enable it and get rid of
>>> redundant code.
>>>
>>> Signed-off-by: Cezary Rojewski <cezary.rojewski@intel.com>
>>
>> This looks like a nice cleanup and I'll happily apply if anyone can
>> test with the actual hardware -- currently mine has no DSP, so unable
>> to check.
>>
>>
>> thanks,
>>
>> Takashi
>>
>
> NHLT override method has been added for internal use half a year ago and
> is for some time the default method within our CI. This is tested on a
> wide spread of hardware, that is any Intel AVS archtecture, including
> production laptops.
We are checking independently with SOF CI [1], the NHLT is used to
detect microphone counts so we'll see if there's a regression.
That said, for my education Cezary an you clarify what you typically
override? the settings are usually tied to specific hardware configs.
Also the NHLT may point to a topology file name but with your recent
changes an alternate file can be used, so it's not clear to me how
non-Intel folks might use the override and for what?
While I am at it, we recently had a bug report where a user provided the
NHLT, and I had no idea how to go about parsing it to check its
contents. Are there any tools to dump the contents in human-readable
representation?
[1] https://github.com/thesofproject/linux/pull/2046
next prev parent reply other threads:[~2020-04-23 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 11:21 [PATCH] ALSA: hda: Refactor Intel NHLT init Cezary Rojewski
2020-04-23 11:24 ` Takashi Iwai
2020-04-23 11:40 ` Cezary Rojewski
2020-04-23 12:15 ` Takashi Iwai
2020-04-23 12:21 ` Cezary Rojewski
2020-04-23 12:24 ` Takashi Iwai
2020-04-23 16:29 ` Pierre-Louis Bossart [this message]
2020-04-23 17:10 ` Cezary Rojewski
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=8e3d7780-d776-d964-d8a8-4618b7ae045a@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=tiwai@suse.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox