[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3194b3d3-5158-472f-9c68-0b0187e2c145@kernel.org>
Date: Tue, 28 Oct 2025 09:41:26 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: "Du, Bin" <bin.du@....com>, mchehab@...nel.org, hverkuil@...all.nl,
laurent.pinchart+renesas@...asonboard.com, bryan.odonoghue@...aro.org,
sakari.ailus@...ux.intel.com, prabhakar.mahadev-lad.rj@...renesas.com,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
sultan@...neltoast.com
Cc: pratap.nirujogi@....com, benjamin.chan@....com, king.li@....com,
gjorgji.rosikopulos@....com, Phil.Jawich@....com, Dominic.Antony@....com,
mario.limonciello@....com, richard.gong@....com, anson.tsao@....com,
Svetoslav Stoilov <Svetoslav.Stoilov@....com>,
Mario Limonciello <superm1@...nel.org>,
Alexey Zagorodnikov <xglooom@...il.com>
Subject: Re: [PATCH v5 1/7] media: platform: amd: Introduce amd isp4 capture
driver
On 28/10/2025 09:30, Du, Bin wrote:
>>> + }
>>> +};
>>> +
>>> +module_platform_driver(isp4_capture_drv);
>>> +
>>> +MODULE_ALIAS("platform:" ISP4_DRV_NAME);
>>
>> You should not need MODULE_ALIAS() in normal cases. If you need it,
>> usually it means your device ID table is wrong (e.g. misses either
>> entries or MODULE_DEVICE_TABLE()). MODULE_ALIAS() is not a substitute
>> for incomplete ID table.
>>
>
> Thanks for the clarification, yes, MODULE_ALIAS() does not apply in our
> case and should be removed.
You don't have ID table, so probably this should be fixed, unless it is
instantiated by some other driver, e.g. as MFD. That's the only typical
use case for alias in the drivers.
Best regards,
Krzysztof
Powered by blists - more mailing lists