Re: (subset) [PATCH v3 0/9] fix reset line polarity for Goodix touchscreen controllers

From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
To: Bjorn Andersson <andersson@kernel.org>,
	samuel@sholland.org, agx@sigxcpu.org, megous@megous.com,
	heiko@sntech.de, hdegoede@redhat.com, robh+dt@kernel.org,
	wens@csie.org, michael.riesch@wolfvision.net, lukma@denx.de,
	icenowy@aosc.io, kernel@pengutronix.de, david@protonic.nl,
	shawnguo@kernel.org, foss+kernel@0leil.net, linux-imx@nxp.com,
	festevam@gmail.com, pgwipeout@gmail.com,
	jagan@amarulasolutions.com, agross@kernel.org, hadess@hadess.net,
	dmitry.torokhov@gmail.com, jernej.skrabec@gmail.com,
	angelogioacchino.delregno@somainline.org, mamlinav@gmail.com,
	frieder.schrempf@kontron.de, angus@akkea.ca,
	Sascha Hauer <s.hauer@pengutronix.de>,
	konrad.dybcio@somainline.org, krzysztof.kozlowski+dt@linaro.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-input@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-sunxi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
	linux-rockchip@lists.infradead.org
Subject: Re: (subset) [PATCH v3 0/9] fix reset line polarity for Goodix touchscreen controllers
Date: Mon, 16 Jan 2023 13:37:25 +0100	[thread overview]
Message-ID: <f6a8a8f1-0eec-2716-d4f1-9115c9d156b6@theobroma-systems.com> (raw)
In-Reply-To: <167336743963.2134489.16668389773212954467.b4-ty@kernel.org>

Hi Bjorn, all,

On 1/10/23 17:17, Bjorn Andersson wrote:
> On Mon, 5 Dec 2022 14:40:29 +0100, Quentin Schulz wrote:
>> From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
>>
>> The Goodix touchscreen controller has a reset line active low. It happens to
>> also be used to configure its i2c address at runtime. If the reset line is
>> incorrectly asserted, the address will be wrongly configured. This cost me a few
>> hours, trying to figure out why the touchscreen wouldn't work.
>>
>> [...]
> 
> Applied, thanks!
> 
> [8/9] arm64: dts: qcom: msm8998-fxtec: fix touchscreen reset GPIO polarity
>        commit: 8a0721dae68fdb4534e220fc9faae7a0ef2f3785
> 

Thank you for the merge, however I think there could be some issue here.

This requires the patches 1, 2 and 3 all modifying the input driver in 
order to not introduce a regression.

I mistakenly removed the RFC tag and seemingly didn't make it clear 
enough that I had some question on how to properly merge this patch 
series, c.f. "Do we also make this patch series only one patchset since 
the DT patches depend
on the driver patch and vice-versa? In which tree would this go?" in the 
cover letter.

So please, how do we go on with the rest of the patch series? Should I 
submit a v4 which would be only one patch with DT and input changes all 
at once and Bjorn reverts the patch they had just merged?

@Dmitry, since you would have to merge at least patches 1 to 3 in your 
tree (I assume), would you be willing to take the DT patches at the same 
time through your tree too? Are the appropriate device DT maintainers OK 
with this?

Cheers,
Quentin