From: Hans de Goede <hdegoede@redhat.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
linux-kernel@vger.kernel.org
Cc: platform-driver-x86@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH 1/3] Input: silead - Add OF device ID table
Date: Wed, 22 Feb 2017 09:29:11 +0100 [thread overview]
Message-ID: <bfea9fbe-663a-69e4-29f1-5e90a8d9e475@redhat.com> (raw)
In-Reply-To: <20170221181254.14748-1-javier@osg.samsung.com>
Hi,
On 21-02-17 19:12, 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.
>
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
> ---
>
> drivers/input/touchscreen/silead.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/drivers/input/touchscreen/silead.c b/drivers/input/touchscreen/silead.c
> index 404830a4a366..aae3ba1c3e02 100644
> --- a/drivers/input/touchscreen/silead.c
> +++ b/drivers/input/touchscreen/silead.c
> @@ -580,12 +580,26 @@ static const struct acpi_device_id silead_ts_acpi_match[] = {
> MODULE_DEVICE_TABLE(acpi, silead_ts_acpi_match);
> #endif
>
> +#ifdef CONFIG_OF
> +static const struct of_device_id silead_ts_of_match[] = {
> + { .compatible = "silead,gsl1680" },
> + { .compatible = "silead,gsl1688" },
> + { .compatible = "silead,gsl3670" },
> + { .compatible = "silead,gsl3675" },
> + { .compatible = "silead,gsl3692" },
> + { .compatible = "silead,mssl1680" },
> + { },
> +};
Please drop the mssl1680 compatible, that id an ACPI ugliness
which we don't need for devicetree.
Otherwise looks good to me.
Regards,
Hans
> +MODULE_DEVICE_TABLE(of, silead_ts_of_match);
> +#endif
> +
> static struct i2c_driver silead_ts_driver = {
> .probe = silead_ts_probe,
> .id_table = silead_ts_id,
> .driver = {
> .name = SILEAD_TS_NAME,
> .acpi_match_table = ACPI_PTR(silead_ts_acpi_match),
> + .of_match_table = of_match_ptr(silead_ts_of_match),
> .pm = &silead_ts_pm,
> },
> };
>
next prev parent reply other threads:[~2017-02-22 8:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 18:12 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
2017-02-23 12:39 ` Javier Martinez Canillas
2017-02-22 8:29 ` Hans de Goede [this message]
2017-02-22 12:45 ` [PATCH 1/3] Input: silead " 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=bfea9fbe-663a-69e4-29f1-5e90a8d9e475@redhat.com \
--to=hdegoede@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=javier@osg.samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®