[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9b073d01-f2fe-a99b-e53c-4a0b3f95ca05@linux.intel.com>
Date: Wed, 10 Mar 2021 10:41:18 -0600
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To: Takashi Iwai <tiwai@...e.de>, Mark Brown <broonie@...nel.org>
Cc: alsa-devel@...a-project.org,
Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
Liam Girdwood <lgirdwood@...il.com>,
linux-kernel@...r.kernel.org, Takashi Iwai <tiwai@...e.com>,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
linux-tegra@...r.kernel.org, Jon Hunter <jonathanh@...dia.com>,
Bard liao <yung-chuan.liao@...ux.intel.com>
Subject: Re: [PATCH V2] ASoC: soc-core: Prevent warning if no DMI table is
present
On 3/10/21 10:37 AM, Takashi Iwai wrote:
> On Wed, 10 Mar 2021 17:18:14 +0100,
> Mark Brown wrote:
>>
>> On Wed, Mar 10, 2021 at 09:44:07AM -0600, Pierre-Louis Bossart wrote:
>>> On 3/10/21 7:35 AM, Mark Brown wrote:
>>
>>>> Just change it to a system level check for ACPI, checking for OF would
>>>> leave problems for board files or any other alternative firmware
>>>> interfaces.
>>
>>> did you mean if (!IS_ENABLED(CONFIG_ACPI)) ?
>>
>> Is there a runtime check?
>
> Well, basically both DMI and ACPI are completely different things, so
> I don't think it's right to check the availability of ACPI as a signal
> of the availability of DMI.
would this work?
if (!IS_ENABLED(CONFIG_DMI))
return 0;
Powered by blists - more mailing lists