From: Javier Martinez Canillas <javier@osg.samsung.com>
To: linux-kernel@vger.kernel.org
Cc: Javier Martinez Canillas <javier@osg.samsung.com>,
Arnd Bergmann <arnd@arndb.de>,
Wei Yongjun <weiyongjun1@huawei.com>,
Serge Semin <fancer.lancer@gmail.com>,
linux-i2c@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
Julia Lawall <julia.lawall@lip6.fr>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Colin Ian King <colin.king@canonical.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: [PATCH 0/4] misc: Add OF device table to I2C drivers that are missing it
Date: Tue, 14 Mar 2017 12:16:34 -0300 [thread overview]
Message-ID: <20170314151638.23132-1-javier@osg.samsung.com> (raw)
Hello,
This series add OF device ID tables to misc I2C drivers whose devices are
either used in Device Tree source files or are listed in binding docs as
a compatible string.
That's done because the plan is to change the I2C core to report proper OF
modaliases instead of always reporting a MODALIAS=i2c:<foo> regardless if
a device was registered via DT or using the legacy platform data mechanism.
So these patches will make sure that misc I2C drivers modules will continue
to be autoloaded once the I2C core is changed to report proper OF modalias.
Best regards,
Javier
Javier Martinez Canillas (4):
misc: tsl2550: Add OF device ID table
misc: ds1682: Add OF device ID table
eeprom: idt_89hpesx: Add OF device ID table
eeprom: at24: Add OF device ID table
drivers/misc/ds1682.c | 7 ++
drivers/misc/eeprom/at24.c | 189 +++++++++++++++++++++++++++++++++++++-
drivers/misc/eeprom/idt_89hpesx.c | 57 ++++++++++++
drivers/misc/tsl2550.c | 7 ++
4 files changed, 259 insertions(+), 1 deletion(-)
--
2.9.3
next reply other threads:[~2017-03-14 15:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 15:16 Javier Martinez Canillas [this message]
2017-03-14 15:16 ` [PATCH 1/4] misc: tsl2550: Add OF device ID table Javier Martinez Canillas
2017-03-14 20:53 ` Arnd Bergmann
2017-03-14 15:16 ` [PATCH 2/4] misc: ds1682: " Javier Martinez Canillas
2017-03-14 20:46 ` Arnd Bergmann
2017-03-15 0:38 ` Javier Martinez Canillas
2017-03-15 3:26 ` Javier Martinez Canillas
2017-03-14 15:16 ` [PATCH 3/4] eeprom: idt_89hpesx: " Javier Martinez Canillas
2017-03-14 15:16 ` [PATCH 4/4] eeprom: at24: " Javier Martinez Canillas
2017-03-14 22:59 ` Andy Shevchenko
2017-03-15 0:15 ` Javier Martinez Canillas
2017-03-15 7:58 ` Wolfram Sang
2017-03-15 10:58 ` Javier Martinez Canillas
2017-03-15 11:21 ` Andy Shevchenko
2017-03-15 11:39 ` Javier Martinez Canillas
2017-03-15 22:43 ` Andy Shevchenko
2017-03-16 12:28 ` Javier Martinez Canillas
2017-03-16 13:07 ` Wolfram Sang
2017-03-16 13:13 ` Javier Martinez Canillas
2017-03-16 13:36 ` Wolfram Sang
2017-03-16 14:07 ` Javier Martinez Canillas
2017-03-16 15:05 ` Wolfram Sang
2017-03-16 15:39 ` Javier Martinez Canillas
2017-03-20 16:45 ` 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=20170314151638.23132-1-javier@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=arnd@arndb.de \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=fancer.lancer@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=weiyongjun1@huawei.com \
--cc=wsa@the-dreams.de \
/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).