linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Jan Engelhardt <jengelh@inai.de>,
	Ben Hutchings <ben@decadent.org.uk>,
	Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: therm_pm72 units, interface
Date: Sat, 03 Aug 2013 07:02:40 +1000	[thread overview]
Message-ID: <1375477360.15999.19.camel@pasglop> (raw)
In-Reply-To: <1375462346.3852.42.camel@thor.local>

On Fri, 2013-08-02 at 18:52 +0200, Michel Dänzer wrote:

> Thanks for the suggestion. The same windfarm modules were loaded in both
> cases, but i2c_powermac wasn't loaded with the newer kernels. Loading it
> manually fixes the problem.
> 
> How is i2c_powermac supposed to get loaded with current kernels?

It's a platform driver, but it's missing a module device-table

Can you try this completely untested patch ?

diff --git a/drivers/i2c/busses/i2c-powermac.c b/drivers/i2c/busses/i2c-powermac.c
index 8dc90da..5af5153 100644
--- a/drivers/i2c/busses/i2c-powermac.c
+++ b/drivers/i2c/busses/i2c-powermac.c
@@ -458,9 +458,15 @@ static int i2c_powermac_probe(struct platform_device *dev)
 	return rc;
 }
 
+static const struct platform_device_id i2c_powermac_id = {
+	.name = "i2c-powermac"
+};
+MODULE_DEVICE_TABLE(platform, i2c_powermac_id);
+
 static struct platform_driver i2c_powermac_driver = {
 	.probe = i2c_powermac_probe,
 	.remove = i2c_powermac_remove,
+	.id_table = *i2c_powermac_id,
 	.driver = {
 		.name = "i2c-powermac",
 		.bus = &platform_bus_type,
@@ -468,5 +474,3 @@ static struct platform_driver i2c_powermac_driver = {
 };
 
 module_platform_driver(i2c_powermac_driver);
-
-MODULE_ALIAS("platform:i2c-powermac");

  reply	other threads:[~2013-08-02 21:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 17:53 therm_pm72 units, interface Jan Engelhardt
2012-08-15 21:35 ` Benjamin Herrenschmidt
2012-08-16 15:24   ` Jan Engelhardt
2012-08-16 20:51     ` Benjamin Herrenschmidt
2012-08-17 13:51       ` Jan Engelhardt
2012-08-17 20:17         ` Benjamin Herrenschmidt
2012-08-17 14:23       ` Jan Engelhardt
2012-08-15 21:36 ` Benjamin Herrenschmidt
2013-01-17 14:38   ` Jan Engelhardt
2013-01-17 23:38     ` Benjamin Herrenschmidt
2013-07-19 17:43       ` Aaro Koskinen
2013-07-19 23:16         ` Benjamin Herrenschmidt
2013-07-20 20:33           ` Aaro Koskinen
2013-07-20 23:42             ` Benjamin Herrenschmidt
2013-08-02 10:03             ` Michel Dänzer
2013-08-02 12:51               ` Benjamin Herrenschmidt
2013-08-02 14:47                 ` Michel Dänzer
2013-08-02 15:58                   ` Aaro Koskinen
2013-08-02 16:52                     ` Michel Dänzer
2013-08-02 21:02                       ` Benjamin Herrenschmidt [this message]
2013-08-05  9:13                         ` Michel Dänzer
2013-08-05  9:22                           ` Benjamin Herrenschmidt
2013-08-05 10:32                             ` Michel Dänzer
2013-08-05 10:53                               ` Benjamin Herrenschmidt
2013-09-27 15:44                                 ` Michel Dänzer
2013-08-02 20:47                   ` Benjamin Herrenschmidt
2013-08-02 20:56                     ` Ben Hutchings
2013-08-02 21:04                       ` Benjamin Herrenschmidt

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=1375477360.15999.19.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=ben@decadent.org.uk \
    --cc=jengelh@inai.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michel@daenzer.net \
    /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;
as well as URLs for NNTP newsgroup(s).