Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: linux-kernel@vger.kernel.org, linux-amarula@amarulasolutions.com,
	Conor Dooley <conor+dt@kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Rob Herring <robh@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Shawn Guo <shawnguo@kernel.org>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 5/6] ARM: dts: imx6ull-engicam-microgea-bmm: set touchscreen glitch threshold
Date: Wed, 17 Sep 2025 12:08:21 -0400	[thread overview]
Message-ID: <aMrc9Z/SNYspPo1l@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250917080534.1772202-6-dario.binacchi@amarulasolutions.com>

On Wed, Sep 17, 2025 at 10:05:10AM +0200, Dario Binacchi wrote:
> This way the detected signal is valid only if it lasts longer than
> 62 µs, otherwise it is not sampled.
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>

Reviewed-by: Frank Li <Frank.Li@nxp.com>

> ---
>
> (no changes since v1)
>
>  arch/arm/boot/dts/nxp/imx/imx6ull-engicam-microgea-bmm.dts | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/nxp/imx/imx6ull-engicam-microgea-bmm.dts b/arch/arm/boot/dts/nxp/imx/imx6ull-engicam-microgea-bmm.dts
> index 279d46c22cd7..f12084d8f2a0 100644
> --- a/arch/arm/boot/dts/nxp/imx/imx6ull-engicam-microgea-bmm.dts
> +++ b/arch/arm/boot/dts/nxp/imx/imx6ull-engicam-microgea-bmm.dts
> @@ -154,6 +154,7 @@ &tsc {
>  	pinctrl-0 = <&pinctrl_tsc>;
>  	measure-delay-time = <0x9ffff>;
>  	pre-charge-time = <0xfff>;
> +	touchscreen-glitch-threshold-ns = <62000>;
>  	xnur-gpios = <&gpio1 3 GPIO_ACTIVE_LOW>;
>  	status = "okay";
>  };
> --
> 2.43.0
>


  reply	other threads:[~2025-09-17 16:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17  8:05 [PATCH v4 0/6] Input: imx6ul_tsc - set glitch threshold by dts property Dario Binacchi
2025-09-17  8:05 ` [PATCH v4 1/6] Input: imx6ul_tsc - fix typo in register name Dario Binacchi
2025-09-18  5:39   ` Dmitry Torokhov
2025-09-17  8:05 ` [PATCH v4 2/6] Input: imx6ul_tsc - use BIT, FIELD_{GET,PREP} and GENMASK macros Dario Binacchi
2025-09-18  5:39   ` Dmitry Torokhov
2025-09-17  8:05 ` [PATCH v4 4/6] dt-bindings: touchscreen: fsl,imx6ul-tsc: support glitch thresold Dario Binacchi
2025-09-17 16:07   ` Frank Li
2025-09-17 19:26     ` Conor Dooley
2025-09-17  8:05 ` [PATCH v4 5/6] ARM: dts: imx6ull-engicam-microgea-bmm: set touchscreen glitch threshold Dario Binacchi
2025-09-17 16:08   ` Frank Li [this message]
2025-09-17  8:05 ` [PATCH v4 6/6] Input: imx6ul_tsc - set glitch threshold by DTS property Dario Binacchi
2025-09-17 16:20   ` Frank Li

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=aMrc9Z/SNYspPo1l@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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