From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 3/3] Input: qt1070 - Add OF device ID table
Date: Thu, 23 Feb 2017 00:27:51 -0800 [thread overview]
Message-ID: <20170223082751.GC18639@dtor-ws> (raw)
In-Reply-To: <20170223082524.GB18639@dtor-ws>
On Thu, Feb 23, 2017 at 12:25:24AM -0800, Dmitry Torokhov wrote:
> On Tue, Feb 21, 2017 at 03:12:54PM -0300, Javier Martinez Canillas wrote:
> > The driver doesn't have a struct of_device_id table but supported devices
> > are registered via Device Trees. This is working on the assumption that a
> > I2C device registered via OF will always match a legacy I2C device ID and
> > that the MODALIAS reported will always be of the form i2c:<device>.
> >
> > But this could change in the future so the correct approach is to have an
> > OF device ID table if the devices are registered via OF.
> >
> > The compatible strings don't have a vendor prefix because that's how it's
> > used currently, and changing this will be a Device Tree ABI break.
>
> Are you saying that all legacy I2C names now form DT ABI? Even for
> drivers that do not have of_match_table or OF MODULE_DEVICE_TABLE not
> binding documentation?
>
> I think this is a bit too much.
Ah, I see that it is actually used in various DTSes.
OK, I think we still need the proper compatible ("atmel,qt1070") along
with the legacy compatible string.
>
> >
> > Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
> > ---
> >
> > drivers/input/keyboard/qt1070.c | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/drivers/input/keyboard/qt1070.c b/drivers/input/keyboard/qt1070.c
> > index 5a5778729e37..76bb51309a78 100644
> > --- a/drivers/input/keyboard/qt1070.c
> > +++ b/drivers/input/keyboard/qt1070.c
> > @@ -274,9 +274,18 @@ static const struct i2c_device_id qt1070_id[] = {
> > };
> > MODULE_DEVICE_TABLE(i2c, qt1070_id);
> >
> > +#ifdef CONFIG_OF
> > +static const struct of_device_id qt1070_of_match[] = {
> > + { .compatible = "qt1070", },
> > + { },
> > +};
> > +MODULE_DEVICE_TABLE(of, qt1070_of_match);
> > +#endif
> > +
> > static struct i2c_driver qt1070_driver = {
> > .driver = {
> > .name = "qt1070",
> > + .of_match_table = of_match_ptr(qt1070_of_match),
> > .pm = &qt1070_pm_ops,
> > },
> > .id_table = qt1070_id,
> > --
> > 2.9.3
> >
>
> --
> Dmitry
--
Dmitry
next prev parent reply other threads:[~2017-02-23 8:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 18:12 [PATCH 1/3] Input: silead - Add OF device ID table Javier Martinez Canillas
2017-02-21 18:12 ` [PATCH 2/3] Input: synaptics_i2c " Javier Martinez Canillas
2017-02-23 8:31 ` Dmitry Torokhov
2017-02-23 12:40 ` Javier Martinez Canillas
2017-02-21 18:12 ` [PATCH 3/3] Input: qt1070 " Javier Martinez Canillas
2017-02-23 8:25 ` Dmitry Torokhov
2017-02-23 8:27 ` Dmitry Torokhov [this message]
2017-02-23 12:39 ` Javier Martinez Canillas
2017-02-22 8:29 ` [PATCH 1/3] Input: silead " Hans de Goede
2017-02-22 12:45 ` Javier Martinez Canillas
2017-02-22 14:23 ` Hans de Goede
2017-02-22 14:25 ` 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=20170223082751.GC18639@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=javier@osg.samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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).