From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Pengyu Luo <mitltlatltl@gmail.com>, konrad.dybcio@oss.qualcomm.com
Cc: andersson@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, konradybcio@kernel.org,
krzk+dt@kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sm8650: Add support for Oneplus Pad Pro (caihong)
Date: Thu, 22 May 2025 17:05:19 +0200 [thread overview]
Message-ID: <53e1127d-77fb-4bb7-a125-18d7afc0d843@oss.qualcomm.com> (raw)
In-Reply-To: <20250521083746.666228-1-mitltlatltl@gmail.com>
On 5/21/25 10:37 AM, Pengyu Luo wrote:
> On Wed, May 21, 2025 at 5:54 AM Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> wrote:
>> On 5/20/25 6:42 PM, Pengyu Luo wrote:
>>> The OnePlus Pad Pro is an Android tablet based on the Qualcomm SM8650
>>> platform. Its device codename is "caihong". This patch adds an initial
>>> devicetree for basic functionality.
[...]
>>> +&i2c2 {
>>> + status = "okay";
>>> +
>>> + /* secondary kinetic,ktz8866@11 */
>>
>> You can describe it, the driver sets some nonzero default brightness
>>
>
> But the backlight framework won't index them, which causes sysfs
> collision when the second instance is registering.
Have you talked to the backlight maintainers? This shouldn't be too
complex to figure out
Konrad
next prev parent reply other threads:[~2025-05-22 15:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 16:42 [PATCH 0/2] arm64: dts: qcom: Introduce Oneplus Pad Pro Pengyu Luo
2025-05-20 16:42 ` [PATCH 1/2] dt-bindings: arm: qcom: Add Oneplus Pad Pro (caihong) Pengyu Luo
2025-05-21 9:58 ` Krzysztof Kozlowski
2025-05-20 16:42 ` [PATCH 2/2] arm64: dts: qcom: sm8650: Add support for " Pengyu Luo
2025-05-20 21:54 ` Konrad Dybcio
2025-05-21 8:37 ` Pengyu Luo
2025-05-21 12:43 ` neil.armstrong
2025-05-22 10:05 ` Pengyu Luo
2025-05-26 7:53 ` neil.armstrong
2025-05-22 15:05 ` Konrad Dybcio [this message]
2025-05-25 10:51 ` Pengyu Luo
2025-05-27 11:11 ` Konrad Dybcio
2025-06-02 13:44 ` Pengyu Luo
2025-05-21 12:49 ` neil.armstrong
2025-05-22 10:05 ` Pengyu Luo
2025-05-26 7:56 ` neil.armstrong
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=53e1127d-77fb-4bb7-a125-18d7afc0d843@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mitltlatltl@gmail.com \
--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®