All of lore.kernel.org
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx6: RDU2: fix eGalax touchscreen node
Date: Fri, 16 Nov 2018 11:02:14 +0800	[thread overview]
Message-ID: <20181116030212.GI5829@dragon> (raw)
In-Reply-To: <20181105173156.3519-1-l.stach@pengutronix.de>

On Mon, Nov 05, 2018 at 06:31:56PM +0100, Lucas Stach wrote:
> Use the correct compatible for the new protocol used by the firmware
> on the touch controller, the GPIO wakeup isn't used in that case.
> Also eGalax touch needs axis swapping, just as with the RMI4 touch.
> 
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>

Applied, thanks.

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
	devicetree@vger.kernel.org, kernel@pengutronix.de,
	linux-arm-kernel@lists.infradead.org,
	patchwork-lst@pengutronix.de
Subject: Re: [PATCH] ARM: dts: imx6: RDU2: fix eGalax touchscreen node
Date: Fri, 16 Nov 2018 11:02:14 +0800	[thread overview]
Message-ID: <20181116030212.GI5829@dragon> (raw)
In-Reply-To: <20181105173156.3519-1-l.stach@pengutronix.de>

On Mon, Nov 05, 2018 at 06:31:56PM +0100, Lucas Stach wrote:
> Use the correct compatible for the new protocol used by the firmware
> on the touch controller, the GPIO wakeup isn't used in that case.
> Also eGalax touch needs axis swapping, just as with the RMI4 touch.
> 
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>

Applied, thanks.

  reply	other threads:[~2018-11-16  3:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05 17:31 [PATCH] ARM: dts: imx6: RDU2: fix eGalax touchscreen node Lucas Stach
2018-11-05 17:31 ` Lucas Stach
2018-11-16  3:02 ` Shawn Guo [this message]
2018-11-16  3:02   ` Shawn Guo

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=20181116030212.GI5829@dragon \
    --to=shawnguo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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.