public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Du, Bin" <bin.du@amd.com>,
	mchehab@kernel.org, hverkuil@xs4all.nl,
	laurent.pinchart+renesas@ideasonboard.com,
	bryan.odonoghue@linaro.org, sakari.ailus@linux.intel.com,
	prabhakar.mahadev-lad.rj@bp.renesas.com,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	sultan@kerneltoast.com
Cc: pratap.nirujogi@amd.com, benjamin.chan@amd.com, king.li@amd.com,
	gjorgji.rosikopulos@amd.com, Phil.Jawich@amd.com,
	Dominic.Antony@amd.com, mario.limonciello@amd.com,
	richard.gong@amd.com, anson.tsao@amd.com,
	Mario Limonciello <superm1@kernel.org>,
	Alexey Zagorodnikov <xglooom@gmail.com>
Subject: Re: [PATCH v5 1/7] media: platform: amd: Introduce amd isp4 capture driver
Date: Tue, 28 Oct 2025 10:06:28 +0100	[thread overview]
Message-ID: <6668e1f8-c279-4616-aaa2-02669895e623@kernel.org> (raw)
In-Reply-To: <7b20fb08-fa96-4bd9-8240-05b7f8f31681@amd.com>

On 28/10/2025 10:00, Du, Bin wrote:
> Thanks Krzysztof.
> 
> On 10/28/2025 4:41 PM, Krzysztof Kozlowski wrote:
>> 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.
>>
> 
> Yes, our device is a MFD, so alias works for it, as alternative, we can 
> add module device table, it should work either, could you please 
> indicate your preferred option?
>


So it is spawned by drivers/gpu/drm/amd/amdgpu/isp_v4_1_0.c or
drivers/gpu/drm/amd/amdgpu/isp_v4_1_1.c ?

If so, then your code is fine, that's correct use of MODULE_ALIAS.

Best regards,
Krzysztof

  reply	other threads:[~2025-10-28  9:06 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24  9:06 [PATCH v5 0/7] Add AMD ISP4 driver Bin Du
2025-10-24  9:06 ` [PATCH v5 1/7] media: platform: amd: Introduce amd isp4 capture driver Bin Du
2025-10-24 13:57   ` Krzysztof Kozlowski
2025-10-28  8:30     ` Du, Bin
2025-10-28  8:41       ` Krzysztof Kozlowski
2025-10-28  9:00         ` Du, Bin
2025-10-28  9:06           ` Krzysztof Kozlowski [this message]
2025-10-28  9:10             ` Du, Bin
2025-11-03  6:17               ` Du, Bin
2025-10-24  9:06 ` [PATCH v5 2/7] media: platform: amd: low level support for isp4 firmware Bin Du
2025-10-24  9:06 ` [PATCH v5 3/7] media: platform: amd: Add isp4 fw and hw interface Bin Du
2025-10-24  9:06 ` [PATCH v5 4/7] media: platform: amd: isp4 subdev and firmware loading handling added Bin Du
2025-10-24  9:06 ` [PATCH v5 5/7] media: platform: amd: isp4 video node and buffers " Bin Du
2025-10-24  9:06 ` [PATCH v5 6/7] media: platform: amd: isp4 debug fs logging and more descriptive errors Bin Du
2025-10-24  9:06 ` [PATCH v5 7/7] Documentation: add documentation of AMD isp 4 driver Bin Du
2025-11-05  9:25 ` [PATCH v5 0/7] Add AMD ISP4 driver Sultan Alsawaf
2025-11-10  8:33   ` Sultan Alsawaf
2025-11-10  9:46     ` Du, Bin
2025-11-11  9:05       ` Sultan Alsawaf
2025-11-11  9:58         ` Du, Bin
2025-11-11 23:33           ` Sultan Alsawaf
2025-11-12  1:21             ` Sultan Alsawaf
2025-11-12  6:32               ` Du, Bin
2025-11-12  7:06                 ` Sultan Alsawaf
2025-11-12  7:38                   ` Sultan Alsawaf
2025-11-12 10:21                     ` Du, Bin
2025-11-18  7:35                       ` Sultan Alsawaf
2025-11-19 10:14                         ` Du, Bin
2025-11-21  8:20                           ` Sultan Alsawaf
2025-11-21 14:32                             ` Mario Limonciello
2025-11-21 15:39                               ` Sultan Alsawaf
2025-11-21 15:46                                 ` Mario Limonciello
2025-11-21 16:31                                   ` Sultan Alsawaf
2025-11-21 17:52                                     ` Mario Limonciello
2025-11-22  2:55                             ` Sultan Alsawaf
2025-11-22  3:19                               ` Sultan Alsawaf
2025-11-25  7:55                                 ` Sultan Alsawaf
2025-11-27  6:16                                   ` Du, Bin
2025-11-27  6:40                                     ` Sultan Alsawaf

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=6668e1f8-c279-4616-aaa2-02669895e623@kernel.org \
    --to=krzk@kernel.org \
    --cc=Dominic.Antony@amd.com \
    --cc=Phil.Jawich@amd.com \
    --cc=anson.tsao@amd.com \
    --cc=benjamin.chan@amd.com \
    --cc=bin.du@amd.com \
    --cc=bryan.odonoghue@linaro.org \
    --cc=gjorgji.rosikopulos@amd.com \
    --cc=hverkuil@xs4all.nl \
    --cc=king.li@amd.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mchehab@kernel.org \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=pratap.nirujogi@amd.com \
    --cc=richard.gong@amd.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sultan@kerneltoast.com \
    --cc=superm1@kernel.org \
    --cc=xglooom@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox