From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org,
Igor Grinberg <grinberg@compulab.co.il>,
Aniroop Mathur <a.mathur@samsung.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH 2/3] Input: synaptics_i2c - Add OF device ID table
Date: Thu, 23 Feb 2017 00:31:43 -0800 [thread overview]
Message-ID: <20170223083143.GD18639@dtor-ws> (raw)
In-Reply-To: <20170221181254.14748-2-javier@osg.samsung.com>
On Tue, Feb 21, 2017 at 03:12:53PM -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.
This driver is for touchpad controller on a specific device, and as far
as I understand, for a specific firmware. I am not sure if it will ever
be reused.
Igor, maybe we need to drop it altogether?
>
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
> ---
>
> drivers/input/mouse/synaptics_i2c.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/input/mouse/synaptics_i2c.c b/drivers/input/mouse/synaptics_i2c.c
> index cb2bf203f4ca..8538318d332c 100644
> --- a/drivers/input/mouse/synaptics_i2c.c
> +++ b/drivers/input/mouse/synaptics_i2c.c
> @@ -652,9 +652,18 @@ static const struct i2c_device_id synaptics_i2c_id_table[] = {
> };
> MODULE_DEVICE_TABLE(i2c, synaptics_i2c_id_table);
>
> +#ifdef CONFIG_OF
> +static const struct of_device_id synaptics_i2c_of_match[] = {
> + { .compatible = "synaptics,synaptics_i2c", },
> + { },
> +};
> +MODULE_DEVICE_TABLE(of, synaptics_i2c_of_match);
> +#endif
> +
> static struct i2c_driver synaptics_i2c_driver = {
> .driver = {
> .name = DRIVER_NAME,
> + .of_match_table = of_match_ptr(synaptics_i2c_of_match),
> .pm = &synaptics_i2c_pm,
> },
>
> --
> 2.9.3
>
--
Dmitry
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
Igor Grinberg <grinberg@compulab.co.il>
Cc: linux-kernel@vger.kernel.org,
Igor Grinberg <grinberg@compulab.co.il>,
Aniroop Mathur <a.mathur@samsung.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH 2/3] Input: synaptics_i2c - Add OF device ID table
Date: Thu, 23 Feb 2017 00:31:43 -0800 [thread overview]
Message-ID: <20170223083143.GD18639@dtor-ws> (raw)
In-Reply-To: <20170221181254.14748-2-javier@osg.samsung.com>
On Tue, Feb 21, 2017 at 03:12:53PM -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.
This driver is for touchpad controller on a specific device, and as far
as I understand, for a specific firmware. I am not sure if it will ever
be reused.
Igor, maybe we need to drop it altogether?
>
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
> ---
>
> drivers/input/mouse/synaptics_i2c.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/input/mouse/synaptics_i2c.c b/drivers/input/mouse/synaptics_i2c.c
> index cb2bf203f4ca..8538318d332c 100644
> --- a/drivers/input/mouse/synaptics_i2c.c
> +++ b/drivers/input/mouse/synaptics_i2c.c
> @@ -652,9 +652,18 @@ static const struct i2c_device_id synaptics_i2c_id_table[] = {
> };
> MODULE_DEVICE_TABLE(i2c, synaptics_i2c_id_table);
>
> +#ifdef CONFIG_OF
> +static const struct of_device_id synaptics_i2c_of_match[] = {
> + { .compatible = "synaptics,synaptics_i2c", },
> + { },
> +};
> +MODULE_DEVICE_TABLE(of, synaptics_i2c_of_match);
> +#endif
> +
> static struct i2c_driver synaptics_i2c_driver = {
> .driver = {
> .name = DRIVER_NAME,
> + .of_match_table = of_match_ptr(synaptics_i2c_of_match),
> .pm = &synaptics_i2c_pm,
> },
>
> --
> 2.9.3
>
--
Dmitry
next prev parent reply other threads:[~2017-02-23 8:40 UTC|newest]
Thread overview: 13+ 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 [this message]
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
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=20170223083143.GD18639@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=a.mathur@samsung.com \
--cc=grinberg@compulab.co.il \
--cc=javier@osg.samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.