linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-input@vger.kernel.org, Nikita Travkin <nikita@trvn.ru>
Subject: Re: [PATCH] Input: zinitix - Add BT404 compatible string
Date: Mon, 14 Feb 2022 14:56:48 -0800	[thread overview]
Message-ID: <YgreMDuxQLKoKmo7@google.com> (raw)
In-Reply-To: <20220213225235.812864-1-linus.walleij@linaro.org>

Hi Linus, Nikita,

On Sun, Feb 13, 2022 at 11:52:35PM +0100, Linus Walleij wrote:
> This driver works just fine with the BT404 version of the touchscreen
> as well. Tested on the Samsung GT-I8160 (Codina) mobile phone.

What about all other compatibles that we added to the binding document?
Do we need to prune them or add them to the driver?

> 
> Cc: Nikita Travkin <nikita@trvn.ru>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
>  drivers/input/touchscreen/zinitix.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/input/touchscreen/zinitix.c b/drivers/input/touchscreen/zinitix.c
> index b7a9c3cbe0b2..dff24899855b 100644
> --- a/drivers/input/touchscreen/zinitix.c
> +++ b/drivers/input/touchscreen/zinitix.c
> @@ -626,6 +626,7 @@ static SIMPLE_DEV_PM_OPS(zinitix_pm_ops, zinitix_suspend, zinitix_resume);
>  
>  #ifdef CONFIG_OF
>  static const struct of_device_id zinitix_of_match[] = {
> +	{ .compatible = "zinitix,bt404" },
>  	{ .compatible = "zinitix,bt532" },
>  	{ .compatible = "zinitix,bt541" },
>  	{ }
> -- 
> 2.34.1
> 

Thanks.

-- 
Dmitry

  reply	other threads:[~2022-02-14 22:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-13 22:52 [PATCH] Input: zinitix - Add BT404 compatible string Linus Walleij
2022-02-14 22:56 ` Dmitry Torokhov [this message]
2022-02-14 23:09   ` Linus Walleij

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=YgreMDuxQLKoKmo7@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-input@vger.kernel.org \
    --cc=nikita@trvn.ru \
    /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).