From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-yx1-f42.google.com (mail-yx1-f42.google.com [74.125.224.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BE32E1CEAD6 for ; Thu, 16 Oct 2025 20:08:28 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=74.125.224.42 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1760645310; cv=none; b=Nfp1NRaFsF9k92ceahr94ndVZNYKIWhBmPAYQeQbjSxJAQ8+9/WUmsaCDVs1HlHfU7KzxTzPtvWXqVbDjEx8aR1/aKJe4OZlSoNbzVALNABb4KO97GXLwG4pXT1UsiAd829s+ogMiTzPYC3PoXsHtswZ+tzp7KWDO8xxwKjo9fc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1760645310; c=relaxed/simple; bh=5LV1LhbZXSqdN8/Ic6BuDFnwHiv8u0GIP1b8uHhLq8A=; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=EVMJnOUuJpKhhUYN23kQiE9EsgDmQam0XyxIMFVfOAjTylV7hUlA9yckswPQubu0qwYjA23MVfExHJdNJKcuI2/NklvGwx9Vk9VAilDPZpOEpm+tUuQVoVHB7/MjvFrbgzIofQvUlUQrM/mbJst/i6dNwaG/wMjw3ImQo6vA58I= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=cQ7Jt8PR; arc=none smtp.client-ip=74.125.224.42 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="cQ7Jt8PR" Received: by mail-yx1-f42.google.com with SMTP id 956f58d0204a3-63e14c509d6so656654d50.0 for ; Thu, 16 Oct 2025 13:08:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1760645308; x=1761250108; darn=vger.kernel.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=zwSJQlIKUBZxKguIzgka47vhsGWXbpweHW396bjpenE=; b=cQ7Jt8PRLP2bdHUqwCjJx2w5q1Bf+uBKQ6jGV7vfm+JVSzm0Og7LGFvKTfl5A7AqY3 jcbaB9wc+kUJhEfh+5d5JnzJNth0AUTvc3zZmuyTlr0Y9nLmWjKVw6JLr6d6PVLcvy2q cWv4HHCSLSW38gyuOn56+Z3Mf3qEm+K79Pp9ZTXJzN8+LUfHrKM4WfhTYICW4+rM6605 +3IKFyENvSOOv2Cci8o6Nbc1Hn7NRy8bOGkmOI2g84uiW6CVTQhYwLkoRZFyw4iASCGl FbYRrJw+YkBPRrl7IcLhbG9obSGor+lD6rChfSX2j89b3IXXSE0sba4o5y4vXrRDGFLz 8RYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1760645308; x=1761250108; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=zwSJQlIKUBZxKguIzgka47vhsGWXbpweHW396bjpenE=; b=DDoKvxiSBcWTkZGguK8mPOzMKtWFmfn7kkU9K/7KVaQ7rGzMj0P5avaTpZFb0VhUVy kpJBm8+RRQMSZRAiV90e5UTtICaH9IFOKLpKfSBmxoG/8SPQNkEnLiX8be6nMKQpKz7W rwR6Vj3bMyG5nvaCLEpLHr9Jcu0tUbPRJq/AoS4i0tlyoZrEsKtNaZHx/iyL1tfLZ4ey Np1PYw2RiCSh6iNHiDHNuhY+G11TXHsHVtqDQJXmSh1gQyYHgAZoUDq8+TGxFst6Rzc5 DiU2GQflON+fYwKNmzSleY/ckuGyVHe7Fq/VB+9P7pxMv6kPrfwx+i9zyDNOuOKC9ES8 cfuw== X-Forwarded-Encrypted: i=1; AJvYcCVgG2g+xmdrnB2ItT/ELJekjufaUjh6lj0wtQ5+xvHAe6kS3jC7oS3JqfN7J32p8hTrQH9Z1FRVIpGf1/ZC@vger.kernel.org X-Gm-Message-State: AOJu0Yx3MTejaXzixv6nyrHzUFeuCPceRA7nCl2uf6Opql7osa63glRv 8e+LIHu2TyRZy/N7wCFsMpUZk8HVKcVqSE2/OQN61ih9LlX6WBw+xhEqwIYc9B5KtewTDYs7VZO /yQxgMFA+bRPJoTQ9IX7B3z0zfjg73n+D5M51qqM= X-Gm-Gg: ASbGncuhVSH439VJNFPrKn3TBMWdFtKYDwlNbvvryHe7E4AFRID94a5r+77vxvNq2SK 2471dmAUDBFaiEffGhLqUXGNTaeWao4mCkAeLbrBIm5IxTXvNNRBY+fSEXUFW4pC/oHT7ta1SE3 40AIOTysWLpEumRPicyoa5+5nHjMA79bpGvfh9nGxrxtWtA9A+iIe4NO1jiY938Bl0laEZXgzGx C/f58hQ44jKvtrhHVmmLZ2o1iSqrjRGBoPX++E0KxufTysaAfZaZkIQyQU= X-Google-Smtp-Source: AGHT+IHvMgZk6If8o2qH54dkg2cytF3aHS8b+WyjiGydzi+xYAEbco+6c2Bb5pN+U9QhO3xEPUlTr6z3Csxk3GbljFI= X-Received: by 2002:a05:690e:11cb:b0:63e:c66:42c2 with SMTP id 956f58d0204a3-63e160d895emr1244040d50.4.1760645307556; Thu, 16 Oct 2025 13:08:27 -0700 (PDT) Precedence: bulk X-Mailing-List: linux-arm-msm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: <20251014044135.177210-1-ghatto404@gmail.com> <20251014044135.177210-4-ghatto404@gmail.com> <8bd5486f-38a9-4104-8d09-234f642b45fe@oss.qualcomm.com> In-Reply-To: <8bd5486f-38a9-4104-8d09-234f642b45fe@oss.qualcomm.com> From: Ghatto Date: Thu, 16 Oct 2025 16:08:15 -0400 X-Gm-Features: AS18NWCRa6pRdMMpu0X_9Af5lgC9aF7fE9-UeKFo7BJK8yxGs2I6QnALReJ2QHs Message-ID: Subject: Re: [PATCH v2 3/6] arm64: dts: qcom: r0q: add touchscreen support To: Konrad Dybcio Cc: Krzysztof Kozlowski , Bjorn Andersson , Konrad Dybcio , Rob Herring , Conor Dooley , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Oct 16, 2025 at 6:06=E2=80=AFAM Konrad Dybcio wrote: > > > > On 10/14/25 9:04 PM, Ghatto wrote: > > On Tue, Oct 14, 2025 at 11:18=E2=80=AFAM Konrad Dybcio > > wrote: > >> > >> On 10/14/25 5:10 PM, Ghatto wrote: > >>> On Tue, Oct 14, 2025 at 7:01=E2=80=AFAM Konrad Dybcio > >>> wrote: > >>>> > >>>> On 10/14/25 6:41 AM, Eric Gon=C3=A7alves wrote: > >>>>> Enable the ST-Microelectronics FTS2BA61Y touchscreen. This patch > >>>>> depends on "Input: add support for the STM FTS2BA61Y touchscreen". > >>>> > >>>> The second sentence doesn't really make sense to be included in > >>>> the git log > >>> I'll keep it to the cover letter then > >>>> > >>>>> The device has an issue where SPI 8 (the bus which the touchscreen = is > >>>>> connected to) is not working properly right now, so > >>>>> spi-gpio is used instead. > >>>> > >>>> Some Samsung devices used to use spi/i2c-gpio intentionally, also > >>>> on downstream. I'm assuming this isn't the case for r0q. > >>> It isn't, the device uses fts2ba61y on the spi8 bus - I hosted the > >>> DT at https://github.com/ghatt-o/ss_experiments/blob/main/r0q.dts if = you > >>> want to take a look. > >>>> > >>>> Did you enable gpi_dma1, qupv3_id_1 before spi8, when testing > >>> The driver probes, but it fails to recognize the touchscreen device > >> > >> Could you post a complete dmesg and the precise DT diff you used? > > https://pastebin.com/QkYa8nMp (android dmesg) mainline dmesg doesn't ha= ve > > The link has expired =F0=9F=99=81 https://pastebin.com/s4abJS9M shouldn't expire now! > > > any relevant information other than spi/i2c probing, however, I've noti= ced > > both on deviceinfohw.ru and the dmesg that for some reason the touchscr= een > > is on spi0.0 (even though DT says 8) and I'm not sure if that means it'= s on SPI > > but on a bugged out bus or if it's really just spi on bus 0 > > It means that it's on the SPI bus that probed first (index 0) > > [...] > > > +&spi8 { > > + spi-max-frequency =3D <5000000>; > > + > > + touchscreen@0 { > > + compatible =3D "st,fts2ba61y"; > > + reg =3D <0>; > > + > > + vdd-supply =3D <&vreg_l8c_1p8>; > > + avdd-supply =3D <&vreg_l11c_3p0>; > > + > > + interrupt-parent =3D <&tlmm>; > > + interrupts =3D <46 IRQ_TYPE_LEVEL_LOW>; > > + > > + pinctrl-names =3D "default", "sleep"; > > + pinctrl-0 =3D <&tsp_int_active>; > > + pinctrl-1 =3D <&tsp_int_sleep>; > > + > > + status =3D "okay"; > > + }; > > + > > + > > + status =3D "okay"; > > +}; > > this won't compile ^ > > Konrad >