From: "Aiqun Yu (Maria)" <quic_aiquny@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
"Rob Herring (Arm)" <robh@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: Remove unused and undocumented properties
Date: Mon, 16 Dec 2024 11:42:18 +0800 [thread overview]
Message-ID: <d3d9dd62-e0cb-4c12-91d1-17ae52688654@quicinc.com> (raw)
In-Reply-To: <68c079b0-defe-4cb0-9f6f-ce9e3645e2ba@oss.qualcomm.com>
On 11/16/2024 3:36 AM, Konrad Dybcio wrote:
> On 15.11.2024 8:34 PM, Rob Herring (Arm) wrote:
>> Remove properties which are both unused in the kernel and undocumented.
>> Most likely they are leftovers from downstream.
>>
>> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
>> ---
>
> Funny, the sideinteraction compatible is undocumented and the touchscreen
> driver is not upstream
Does the compatible also need to be fixed to "focaltech,ft8719"? Refer
to the info from [1].
Confirmed, the compatible "focaltech,fts8719" is not even in any merged
bindings or drivers. Instead, "focaltech,ft8719" is in the current
driver and bindings.
By the way, I am curious about how Rob finds the unused properties.
Could you share some steps?
[1]https://lore.kernel.org/all/Zk4tLPn277Azd4XZ@google.com/
--
Thx and BRs,
Aiqun(Maria) Yu
next prev parent reply other threads:[~2024-12-16 3:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 19:34 Rob Herring (Arm)
2024-11-15 19:36 ` Konrad Dybcio
2024-12-16 3:42 ` Aiqun Yu (Maria) [this message]
2024-12-16 12:41 ` Konrad Dybcio
2024-12-16 14:00 ` Rob Herring
2024-12-18 9:44 ` Aiqun Yu (Maria)
2025-01-08 22:51 ` Bjorn Andersson
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=d3d9dd62-e0cb-4c12-91d1-17ae52688654@quicinc.com \
--to=quic_aiquny@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®