From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Rudraksha Gupta <guptarud@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, beomho.seo@samsung.com,
jcsing.lee@samsung.com, linux-input@vger.kernel.org,
nick.reitemeyer@web.de
Subject: Re: [PATCH] ARM: dts: qcom: msm8960: expressatt: Add coreriver,tc360-touchkey
Date: Tue, 24 Feb 2026 12:28:00 +0100 [thread overview]
Message-ID: <5a86ca7b-9356-4241-a09d-47d37fbc3a18@oss.qualcomm.com> (raw)
In-Reply-To: <41b4f4c1-f0c3-4ce7-8267-039bb77ea953@gmail.com>
On 2/24/26 2:00 AM, Rudraksha Gupta wrote:
>
> On 2/22/26 19:54, Dmitry Torokhov wrote:
>> Hi Rudraksha,
>>
>> On Thu, Feb 19, 2026 at 08:33:43PM -0800, Rudraksha Gupta wrote:
>>> Hello all,
>>>
>>>
>>> Top posting for once (context below).
>>>
>>> Not too sure what the next steps are to get the tm2 touchkey in. Should I
>>> resend the patch, contact someone else that can help provide guidance, or
>>> something else?
>>>
>>>
>>> Adding Dmitry Torokhov (official maintainer) and Nick Reitemeyer (person who
>>> introduced this variant).
>> Sorry, I am not sure what the question is... It seems that you made the
>> driver work without any additional changes?
>
> I believe this patch is blocked on Konrad's comment:
>
>> This driver mentions a register called CYPRESS_MODULE_VER - maybe
> it could help confirm the model?
>
>
> This was in response to me saying that the "coreriver,tc360-touchkey" tm2 variant works as is on my device, but I can't tell for sure if this is actually the variant that is on my device. There isn't really any documentation for how this peripheral works and I was primarily relying on others in this thread to provide details to confirm that this is the actual variant being used.
>
> If I'm mistaken that this is a blocker, please let me know.
That was a suggestion - if we're not able to find out, then we're not
able to find out!
Konrad
prev parent reply other threads:[~2026-02-24 11:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 10:16 Rudraksha Gupta via B4 Relay
2025-12-06 2:18 ` Dmitry Baryshkov
2025-12-06 3:54 ` Rudraksha Gupta
2025-12-06 4:01 ` Dmitry Baryshkov
2025-12-08 16:35 ` Konrad Dybcio
2025-12-09 7:10 ` Rudraksha Gupta
2025-12-16 12:59 ` Konrad Dybcio
2026-02-20 4:33 ` Rudraksha Gupta
2026-02-23 3:54 ` Dmitry Torokhov
2026-02-24 1:00 ` Rudraksha Gupta
2026-02-24 11:28 ` Konrad Dybcio [this message]
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=5a86ca7b-9356-4241-a09d-47d37fbc3a18@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=beomho.seo@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=guptarud@gmail.com \
--cc=jcsing.lee@samsung.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick.reitemeyer@web.de \
--cc=robh@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
all inboxes | Powered by JetHome®