From: Krzysztof Kozlowski <krzk@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH 1/3 v2] Input: atmel_mxt_ts - Fix up inverted RESET handler
Date: Thu, 5 Nov 2020 09:09:00 +0100 [thread overview]
Message-ID: <20201105080900.GA17235@kozik-lap> (raw)
In-Reply-To: <20201104153032.1387747-1-linus.walleij@linaro.org>
On Wed, Nov 04, 2020 at 04:30:30PM +0100, Linus Walleij wrote:
> This driver uses GPIO descriptors to drive the touchscreen
> RESET line. In the existing device trees this has in
> conflict with intution been flagged as GPIO_ACTIVE_HIGH
> and the driver then applies the reverse action by
> driving the line low (setting to 0) to enter
> reset state and driving the line high (setting to 1) to
> get out of reset state.
>
> The correct way to handle active low GPIO lines is to
> provide the GPIO_ACTIVE_LOW in the device tree (thus
> properly describing the hardware) and letting the GPIO
> framework invert the assertion (driving high) to a low
> level and vice versa.
>
> This is considered a bug since the device trees are
> incorrectly mis-specifying the line as active high.
>
> Fix the driver and all device trees specifying a reset
> line.
>
> Cc: Krzysztof Kozlowski <krzk@kernel.org>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-tegra@vger.kernel.org
> Cc: linux-samsung-soc@vger.kernel.org
> Cc: NXP Linux Team <linux-imx@nxp.com>
> Cc: Pengutronix Kernel Team <kernel@pengutronix.de>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v1->v2:
> - New patch fixing this confusion before adding the
> new YAML bindings.
> - CC some misc maintainers and mailing lists that should
> be aware that we do this change.
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-samsung-soc@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-input@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3 v2] Input: atmel_mxt_ts - Fix up inverted RESET handler
Date: Thu, 5 Nov 2020 09:09:00 +0100 [thread overview]
Message-ID: <20201105080900.GA17235@kozik-lap> (raw)
In-Reply-To: <20201104153032.1387747-1-linus.walleij@linaro.org>
On Wed, Nov 04, 2020 at 04:30:30PM +0100, Linus Walleij wrote:
> This driver uses GPIO descriptors to drive the touchscreen
> RESET line. In the existing device trees this has in
> conflict with intution been flagged as GPIO_ACTIVE_HIGH
> and the driver then applies the reverse action by
> driving the line low (setting to 0) to enter
> reset state and driving the line high (setting to 1) to
> get out of reset state.
>
> The correct way to handle active low GPIO lines is to
> provide the GPIO_ACTIVE_LOW in the device tree (thus
> properly describing the hardware) and letting the GPIO
> framework invert the assertion (driving high) to a low
> level and vice versa.
>
> This is considered a bug since the device trees are
> incorrectly mis-specifying the line as active high.
>
> Fix the driver and all device trees specifying a reset
> line.
>
> Cc: Krzysztof Kozlowski <krzk@kernel.org>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-tegra@vger.kernel.org
> Cc: linux-samsung-soc@vger.kernel.org
> Cc: NXP Linux Team <linux-imx@nxp.com>
> Cc: Pengutronix Kernel Team <kernel@pengutronix.de>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v1->v2:
> - New patch fixing this confusion before adding the
> new YAML bindings.
> - CC some misc maintainers and mailing lists that should
> be aware that we do this change.
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-05 8:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 15:30 [PATCH 1/3 v2] Input: atmel_mxt_ts - Fix up inverted RESET handler Linus Walleij
2020-11-04 15:30 ` Linus Walleij
2020-11-04 15:30 ` [PATCH 2/3 v2] Input: atmel_mxt_ts - Convert bindings to YAML and extend Linus Walleij
2020-11-09 17:30 ` Rob Herring
2020-11-23 6:48 ` Dmitry Torokhov
2020-11-04 15:30 ` [PATCH 3/3 v2] Input: atmel_mxt_ts - Support regulator supplies Linus Walleij
2020-11-23 6:48 ` Dmitry Torokhov
2020-11-04 15:59 ` [PATCH 1/3 v2] Input: atmel_mxt_ts - Fix up inverted RESET handler Philippe Schenker
2020-11-04 15:59 ` Philippe Schenker
2020-11-05 8:09 ` Krzysztof Kozlowski [this message]
2020-11-05 8:09 ` Krzysztof Kozlowski
2020-11-23 6:48 ` Dmitry Torokhov
2020-11-23 6:48 ` 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=20201105080900.GA17235@kozik-lap \
--to=krzk@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-tegra@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.