All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: kernel@undef.tools, hadess@hadess.net, dmitry.torokhov@gmail.com,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: phone-devel@vger.kernel.org, megi@xff.cz
Subject: Re: [PATCH] Input: goodix: Add support for GT1158
Date: Tue, 9 Aug 2022 12:18:18 +0200	[thread overview]
Message-ID: <7f2c7594-97bd-c824-9f3d-01514e6b38b1@redhat.com> (raw)
In-Reply-To: <20220809091200.290492-1-kernel@undef.tools>

Hi,

On 8/9/22 11:12, kernel@undef.tools wrote:
> From: Ondrej Jirman <megi@xff.cz>
> 
> This controller is used by PinePhone and PinePhone Pro. Support for
> the PinePhone Pro will be added in a later patch set.
> 
> Signed-off-by: Ondrej Jirman <megi@xff.cz>
> Signed-off-by: Jarrah Gosbell <kernel@undef.tools>

Thanks, patch looks good to me:

Reviewed-by: Hans de Goede <hdegoede@redhat.com>

Regards,

Hans


> ---
>  drivers/input/touchscreen/goodix.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/input/touchscreen/goodix.c b/drivers/input/touchscreen/goodix.c
> index aa45a9fee6a0..06d4fcafb766 100644
> --- a/drivers/input/touchscreen/goodix.c
> +++ b/drivers/input/touchscreen/goodix.c
> @@ -95,6 +95,7 @@ static const struct goodix_chip_data gt9x_chip_data = {
>  
>  static const struct goodix_chip_id goodix_chip_ids[] = {
>  	{ .id = "1151", .data = &gt1x_chip_data },
> +	{ .id = "1158", .data = &gt1x_chip_data },
>  	{ .id = "5663", .data = &gt1x_chip_data },
>  	{ .id = "5688", .data = &gt1x_chip_data },
>  	{ .id = "917S", .data = &gt1x_chip_data },


  reply	other threads:[~2022-08-09 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09  9:12 [PATCH] Input: goodix: Add support for GT1158 kernel
2022-08-09 10:18 ` Hans de Goede [this message]
2022-08-11 23:18 ` Dmitry Torokhov

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=7f2c7594-97bd-c824-9f3d-01514e6b38b1@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hadess@hadess.net \
    --cc=kernel@undef.tools \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=megi@xff.cz \
    --cc=phone-devel@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.