From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH 4/4] eeprom: at24: Add OF device ID table
Date: Wed, 15 Mar 2017 08:39:19 -0300 [thread overview]
Message-ID: <1bfce335-7a66-9905-b196-47366bf73d37@osg.samsung.com> (raw)
In-Reply-To: <CAHp75VeU76YZUA45BO6uBrERfCqoZOow=oLvxauy8WY5adGZ+Q@mail.gmail.com>
Hello Andy,
On 03/15/2017 08:21 AM, Andy Shevchenko wrote:
> On Wed, Mar 15, 2017 at 12:58 PM, Javier Martinez Canillas
> <javier@osg.samsung.com> wrote:
>> On 03/15/2017 04:58 AM, Wolfram Sang wrote:
>
>> Unfortunately some maintainers do and don't accept patches adding I2C tables
>> only to have module autoloading working so I still think it should be fixed.
>
> Wait, how does it work for now?!
>
It only works if you have an I2C device ID table, but that may not be the case
for DT-only drivers that could only have an OF device ID table. In the latter
case module autoload won't work.
> Sounds for me you are trying to solve non-existing issue.
>
It's an existing issue. You _must_ have an I2C device ID table if you want to
autload a device driver which is superfluous for DT-only drivers.
In other words, if you register an I2C device using OF the modalias will be:
$ cat /sys/class/i2c-adapter/i2c-8/8-004b/modalias
i2c:maxtouch
While the correct thing to report should be:
$ cat /sys/class/i2c-adapter/i2c-8/8-004b/modalias
of:NtrackpadT<NULL>Catmel,maxtouch
>> [0]: https://patchwork.kernel.org/patch/6903991/
>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2017-03-15 11:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 15:16 [PATCH 0/4] misc: Add OF device table to I2C drivers that are missing it Javier Martinez Canillas
2017-03-14 15:16 ` [PATCH 4/4] eeprom: at24: Add OF device ID table 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 [this message]
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=1bfce335-7a66-9905-b196-47366bf73d37@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=andy.shevchenko@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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