From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wentong Wu <wentong.wu@intel.com>,
gregkh@linuxfoundation.org, tomas.winkler@intel.com,
hdegoede@redhat.com
Cc: andriy.shevchenko@linux.intel.com, sakari.ailus@linux.intel.com,
alexander.usyskin@intel.com, zhifeng.wang@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mei: Add MEI hardware support for IVSC device
Date: Wed, 29 Nov 2023 13:28:20 +0100 [thread overview]
Message-ID: <954c8f3f-8093-42bb-b817-c9050d27ca3f@kernel.org> (raw)
In-Reply-To: <1701174846-16316-3-git-send-email-wentong.wu@intel.com>
On 28/11/2023 13:34, Wentong Wu wrote:
> The protocol used for the IVSC device to communicate with HOST is MEI.
> The MEI hardware interfaces for the IVSC device are implemented.
>
...
> +static DEFINE_SIMPLE_DEV_PM_OPS(mei_vsc_pm_ops, mei_vsc_suspend, mei_vsc_resume);
> +
> +static struct platform_driver mei_vsc_drv = {
> + .probe = mei_vsc_probe,
> + .remove = mei_vsc_remove,
> + .driver = {
> + .name = "intel_vsc",
> + .pm = &mei_vsc_pm_ops,
> + .probe_type = PROBE_PREFER_ASYNCHRONOUS,
> + },
> +};
> +module_platform_driver(mei_vsc_drv);
> +
> +MODULE_AUTHOR("Wentong Wu <wentong.wu@intel.com>");
> +MODULE_AUTHOR("Zhifeng Wang <zhifeng.wang@intel.com>");
> +MODULE_DESCRIPTION("Intel Visual Sensing Controller Interface");
> +MODULE_ALIAS("platform:intel_vsc");
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.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-11-29 12:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 12:34 [PATCH 0/2] mei: Add support for IVSC device Wentong Wu
2023-11-28 12:34 ` [PATCH 1/2] mei: Add transport driver " Wentong Wu
2023-12-06 7:40 ` Winkler, Tomas
2023-11-28 12:34 ` [PATCH 2/2] mei: Add MEI hardware support " Wentong Wu
2023-11-28 22:50 ` kernel test robot
2023-11-29 9:26 ` Sakari Ailus
2023-11-29 10:21 ` Andy Shevchenko
2023-11-29 10:26 ` Sakari Ailus
2023-11-29 14:11 ` Wu, Wentong
2023-11-29 12:28 ` Krzysztof Kozlowski [this message]
2023-11-29 13:56 ` Wu, Wentong
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=954c8f3f-8093-42bb-b817-c9050d27ca3f@kernel.org \
--to=krzk@kernel.org \
--cc=alexander.usyskin@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomas.winkler@intel.com \
--cc=wentong.wu@intel.com \
--cc=zhifeng.wang@intel.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