mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pengyu Luo <mitltlatltl@gmail.com>
To: 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, mitltlatltl@gmail.com,
	robh@kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sm8650: Add support for Oneplus Pad Pro (caihong)
Date: Mon,  2 Jun 2025 21:44:30 +0800	[thread overview]
Message-ID: <20250602134431.114469-1-mitltlatltl@gmail.com> (raw)
In-Reply-To: <2e052c11-f22c-4d95-841e-cb4665d02451@oss.qualcomm.com>

On Tue, May 27, 2025 at 7:11 PM Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> wrote:
> On 5/25/25 12:51 PM, Pengyu Luo wrote:
> > On Thu, May 22, 2025 at 11:05 PM Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> wrote:
> >> 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
> >
> > Last time I tried to touch ktz8866 source, the reviewer advised me to
> > add an backlight API to register the secondary devie. Since I am still
> > working on the other parts when I am free, it remains unresolved. Now
> > that you reminded me, then I tried to do it.
> >
> > https://lore.kernel.org/linux-fbdev/20250525104022.1326997-1-mitltlatltl@gmail.com/
>
> I think this should be made more generic, so that devices with e.g.
> quad backlight can be easily accommodated for too.. Perhaps you could
> do something like PLATFORM_DEVID_AUTO with incrementing suffixes and

Agree, thanks.

> make `backlight = <&foo>;` on the panel accept an array of devices
> that would be controlled together

In this way, we keep them independent, but we control every backlight
in drm_panel. The questions are the systemd and distribution(sorry, I
am just a junior, I use them). Generally, the systemd will create
serivce for every backlight sysfs. I encountered that they saved
different backlight values, even if I set the same value manually.
As for distribution, it seems that only half backlight is controlled.
I encountered that only half backlight got dimmed.

Best wishes,
Pengyu

  reply	other threads:[~2025-06-02 13:44 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
2025-05-25 10:51         ` Pengyu Luo
2025-05-27 11:11           ` Konrad Dybcio
2025-06-02 13:44             ` Pengyu Luo [this message]
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=20250602134431.114469-1-mitltlatltl@gmail.com \
    --to=mitltlatltl@gmail.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®