linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: a.zummo@towertech.it
Cc: linuxppc-dev@ozlabs.org
Subject: [PATCH] rtc-pcf8563: Add device ids table
Date: Thu, 17 Apr 2008 17:02:58 +0200	[thread overview]
Message-ID: <200804171702.59562.laurentp@cse-semaphore.com> (raw)

Hi,

here's a patch against 2.6.25-rc8-mm2 that adds support for device tree names
to the rtc-pcf8563 driver.

Is the new-style driver conversion patch in 2.6.25-rc8-mm2 scheduled for
2.6.26 ?

--

This patch adds support for device tree names via the i2c mod alias mechanism
to the rtc-pcf8563 driver.

Signed-off-by: Laurent Pinchart <laurentp@cse-semaphore.com>
---
 drivers/rtc/rtc-pcf8563.c |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/drivers/rtc/rtc-pcf8563.c b/drivers/rtc/rtc-pcf8563.c
index a1e2f39..9667a3f 100644
--- a/drivers/rtc/rtc-pcf8563.c
+++ b/drivers/rtc/rtc-pcf8563.c
@@ -299,12 +299,20 @@ static int pcf8563_remove(struct i2c_client *client)
 	return 0;
 }
 
+static struct i2c_device_id pcf8563_id[] = {
+	{ "pcf8563", 0 },
+	{ "rtc8564", 0 },
+	{},
+};
+MODULE_DEVICE_TABLE(i2c, pcf8563_id);
+
 static struct i2c_driver pcf8563_driver = {
 	.driver		= {
 		.name	= "rtc-pcf8563",
 	},
 	.probe		= pcf8563_probe,
 	.remove		= pcf8563_remove,
+	.id_table	= pcf8563_id,
 };
 
 static int __init pcf8563_init(void)
-- 
1.5.0


-- 
Laurent Pinchart
CSE Semaphore Belgium

Chaussee de Bruxelles, 732A
B-1410 Waterloo
Belgium

T +32 (2) 387 42 59
F +32 (2) 387 42 75

             reply	other threads:[~2008-04-17 15:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-17 15:02 Laurent Pinchart [this message]
2008-04-17 15:05 ` [PATCH] rtc-pcf8563: Add device ids table Kumar Gala
     [not found] <200804171708.32847.laurentp@cse-semaphore.com>
     [not found] ` <20080418235451.2643183b@i1501.lan.towertech.it>
     [not found]   ` <20080419113417.19f5567a@hyperion.delvare>
     [not found]     ` <4809EF23.7070902@scram.de>
     [not found]       ` <20080419162358.746b714c@hyperion.delvare>
2008-04-19 16:43         ` Jochen Friedrich
2008-04-21 11:56           ` Laurent Pinchart
2008-04-21 12:12             ` Stefan Roese
2008-04-23 11:09               ` Jean Delvare
2008-04-23 11:35                 ` Stefan Roese
2008-04-23 11:45                   ` Jochen Friedrich
2008-04-22 14:11           ` Laurent Pinchart
2008-04-23 11:16             ` Jean Delvare
2008-04-23 12:12               ` Laurent Pinchart
2008-04-23 12:47                 ` Jean Delvare
2008-04-23 13:26                   ` Jochen Friedrich
2008-04-23 13:46                     ` Jon Smirl
2008-04-27 12:18                     ` Jean Delvare
2008-04-23 13:53                   ` Laurent Pinchart
2008-04-23 13:11               ` Jon Smirl

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=200804171702.59562.laurentp@cse-semaphore.com \
    --to=laurentp@cse-semaphore.com \
    --cc=a.zummo@towertech.it \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).