From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pavan Holla <pholla@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Subject: Re: [PATCH 3/3] platform/chrome: cros_ec_ucsi: Implement UCSI PDC driver
Date: Tue, 26 Mar 2024 09:46:26 +0100 [thread overview]
Message-ID: <a885b792-6c88-4c01-b17f-6dfb11b8fd0c@kernel.org> (raw)
In-Reply-To: <20240325-public-ucsi-h-v1-3-7c7e888edc0a@chromium.org>
On 26/03/2024 00:37, Pavan Holla wrote:
> Implementation of transport driver for UCSI. This driver will be used
> if the ChromeOS EC implements a PPM.
>
> +static struct platform_driver cros_ucsi_driver = {
> + .driver = {
> + .name = DRV_NAME,
> + .pm = &cros_ucsi_pm_ops,
> + },
> + .probe = cros_ucsi_probe,
> + .remove = cros_ucsi_remove,
> +};
> +
> +module_platform_driver(cros_ucsi_driver);
> +
> +MODULE_LICENSE("GPL");
> +MODULE_DESCRIPTION("UCSI driver for ChromeOS EC.");
> +MODULE_ALIAS("platform:" 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.
Using DRV_NAME here brings even more confusion...
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-03-26 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 23:37 [PATCH 0/3] usb: typec: Implement UCSI driver for ChromeOS Pavan Holla
2024-03-25 23:37 ` [PATCH 1/3] usb: typec: ucsi: Provide interface for UCSI transport Pavan Holla
2024-03-26 9:12 ` Greg Kroah-Hartman
2024-03-26 23:48 ` Pavan Holla
2024-03-25 23:37 ` [PATCH 2/3] usb: typec: ucsi: Import " Pavan Holla
2024-03-26 2:11 ` Prashant Malani
2024-03-27 3:46 ` Pavan Holla
2024-03-25 23:37 ` [PATCH 3/3] platform/chrome: cros_ec_ucsi: Implement UCSI PDC driver Pavan Holla
2024-03-26 8:46 ` Krzysztof Kozlowski [this message]
2024-03-26 23:47 ` kernel test robot
2024-03-28 9:05 ` kernel test robot
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=a885b792-6c88-4c01-b17f-6dfb11b8fd0c@kernel.org \
--to=krzk@kernel.org \
--cc=abhishekpandit@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pholla@chromium.org \
/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
all inboxes | Powered by JetHome®