[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1f2943e2-f1f0-449d-a1f2-937bae6a0af9@amd.com>
Date: Fri, 27 Oct 2023 23:02:39 +0530
From: syed saba kareem <ssabakar@....com>
To: Mark Brown <broonie@...nel.org>,
Mario Limonciello <mario.limonciello@....com>
Cc: Krzysztof Kozlowski <krzk@...nel.org>,
Syed Saba Kareem <Syed.SabaKareem@....com>,
alsa-devel@...a-project.org, Vijendar.Mukunda@....com,
Basavaraj.Hiregoudar@....com, Sunil-kumar.Dommati@....com,
venkataprasad.potturu@....com, arungopal.kondaveeti@....com,
mastan.katragadda@....com, juan.martinez@....com,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Marian Postevca <posteuca@...ex.one>,
Alper Nebi Yasak <alpernebiyasak@...il.com>,
Claudiu Beznea <claudiu.beznea@...rochip.com>,
Gaosheng Cui <cuigaosheng1@...wei.com>,
Jarkko Nikula <jarkko.nikula@...mer.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 09/13] ASoC: amd: acp: add machine driver support for pdm
use case
On 10/27/23 21:53, Mark Brown wrote:
> On Fri, Oct 27, 2023 at 10:54:47AM -0500, Mario Limonciello wrote:
>
>> What would actually go into MODULE_DEVICE_TABLE?
>> The platform devices created are contingent upon what was found during the
>> top level ACP driver probe. You don't want all the "child" platform drivers
>> to load unless they're needed.
> You want
>
> MODULE_DEVICE_TABLE(platform, board_ids);
>
> which is effectively the same as all the MODULE_ALIAS items you have
> there (which can be removed).
@krzk:as Mark Brown explained we can use platform device id table
instead of MODULE_ALIAS. As effectively there is no difference between
using platform device id table and MODULE_ALIAS.
If you are still expecting us to use platform id table instead of
MODULE_ALIAS
we will provide the changes as an incremental patch.
Powered by blists - more mailing lists