From: Javier Martinez Canillas <javier@osg.samsung.com>
To: linux-kernel@vger.kernel.org
Cc: Javier Martinez Canillas <javier@osg.samsung.com>,
Zhang Rui <rui.zhang@intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
linux-pm@vger.kernel.org
Subject: [PATCH 1/3] thermal: max77620: Fix module autoload
Date: Fri, 14 Oct 2016 11:35:00 -0300 [thread overview]
Message-ID: <1476455702-21748-2-git-send-email-javier@osg.samsung.com> (raw)
In-Reply-To: <1476455702-21748-1-git-send-email-javier@osg.samsung.com>
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drivers/thermal/max77620_thermal.ko | grep alias
$
After this patch:
$ modinfo drivers/thermal/max77620_thermal.ko | grep alias
alias: platform:max77620-thermal
Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
---
drivers/thermal/max77620_thermal.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/thermal/max77620_thermal.c b/drivers/thermal/max77620_thermal.c
index 83905ff46e40..e9a1fe342760 100644
--- a/drivers/thermal/max77620_thermal.c
+++ b/drivers/thermal/max77620_thermal.c
@@ -149,6 +149,7 @@ static struct platform_device_id max77620_thermal_devtype[] = {
{ .name = "max77620-thermal", },
{},
};
+MODULE_DEVICE_TABLE(platform, max77620_thermal_devtype);
static struct platform_driver max77620_thermal_driver = {
.driver = {
--
2.7.4
next prev parent reply other threads:[~2016-10-14 14:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 14:34 [PATCH 0/3] thermal: Fix module autoload for drivers Javier Martinez Canillas
2016-10-14 14:34 ` Javier Martinez Canillas
2016-10-14 14:35 ` Javier Martinez Canillas [this message]
2016-10-14 14:35 ` [PATCH 2/3] thermal: tango: Fix module autoload Javier Martinez Canillas
2016-10-14 14:35 ` Javier Martinez Canillas
2016-10-14 15:27 ` Marc Gonzalez
2016-10-14 15:27 ` Marc Gonzalez
2016-10-14 15:27 ` Marc Gonzalez
2016-10-14 14:35 ` [PATCH 3/3] thermal: db8500: " Javier Martinez Canillas
2016-11-17 11:50 ` [PATCH 0/3] thermal: Fix module autoload for drivers Javier Martinez Canillas
2016-11-17 11:50 ` Javier Martinez Canillas
2016-11-17 11:50 ` Javier Martinez Canillas
2016-11-17 14:53 ` Eduardo Valentin
2016-11-17 14:53 ` Eduardo Valentin
2016-11-17 14:53 ` Eduardo Valentin
2016-11-17 14:58 ` Javier Martinez Canillas
2016-11-17 14:58 ` Javier Martinez Canillas
2016-11-17 14:58 ` Javier Martinez Canillas
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=1476455702-21748-2-git-send-email-javier@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.