devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pengyu Luo <mitltlatltl@gmail.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	aliceryhl@google.com,  andersson@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org,  ebiggers@google.com,
	ilpo.jarvinen@linux.intel.com, joel.granados@kernel.org,
	 konradybcio@kernel.org, krzk+dt@kernel.org, len.brown@intel.com,
	 linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 lossin@kernel.org, mingo@kernel.org, ojeda@kernel.org,
	robh@kernel.org,  sfr@canb.auug.org.au, vanyang@smail.nju.edu.cn,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH 3/4] arm64: dts: qcom: sc8280xp: Add initial support for Ntmer TW220
Date: Sun, 3 Aug 2025 11:36:07 +0800	[thread overview]
Message-ID: <CAH2e8h6oN1VYevLe1NPpvcAjDjUNBrGUtEWy9y3pDhboCjabMA@mail.gmail.com> (raw)
In-Reply-To: <t7fbgze3hnwbget5nkf3i2rd22pk5vufyimiiec5i7rblzb7x4@rtiuwnyfbmtb>

On Sat, Aug 2, 2025 at 1:27 AM Dmitry Baryshkov
<dmitry.baryshkov@oss.qualcomm.com> wrote:
>
> On Fri, Aug 01, 2025 at 10:27:33PM +0800, Pengyu Luo wrote:
> > On Fri, Aug 1, 2025 at 8:29 PM Konrad Dybcio
> > <konrad.dybcio@oss.qualcomm.com> wrote:
> > >
> > > On 7/31/25 5:05 AM, Pengyu Luo wrote:
> > > > Linux:
> > > >> ae94000 20050001 000001f3 0000000b dddd1011
> > > >> ae94010 00009130 31211101 3e2e1e0e 00001900
> > > >> ae94020 00000000 05190019 064c000c 065f0528
> > > >> ae94030 00060000 00000000 00040000 14000000
> > > >> ae94040 06100006 00003c2c 00001000 00000008
> > > > Windows:
> > > >> ae94000 20050001 000001f7 00000008 00001010
> > > >> ae94010 00009130 31211101 3e2e1e0e 00001900
> > > >> ae94020 00000000 05320032 064c000c 065f0551
> > > >> ae94030 000c0000 00000000 00040000 14000000
> > > >> ae94040 00100008 00013c2c 9bb9b000 00000004
> > >
> > > 0xae94008 differs, bits 0 and 1 say that the cmd mode engine
> > > is busy doing something (did you set MIPI_DSI_MODE_VIDEO?)
> > >
> >
> > Yes. I can confirm MIPI_DSI_MODE_VIDEO is set.
> >
> > Speaking of cmd mode, I still have no idea why DSI_CTRL_CMD_MODE_EN
> > (BIT(2) of 0xae94004) is enabled on Windows.
> >
> > > 0xae94024 says:
> > > Linux:
> > > ACTIVE_H_END=1305
> > > ACTIVE_H_START=25
> > > Windows:
> > > ACTIVE_H_END=1330
> > > ACTIVE_H_START=50
> > >
> > > 0xae9402c:
> > > Linux:
> > > VTOTAL=1631
> > > HTOTAL=1320
> > > Windows:
> > > VTOTAL=1631
> > > HTOTAL=1361
> > >
> > > 0xae94030:
> > > Linux:
> > > HS_END=6
> > > Windows:
> > > HS_END=12
> > >
> >
> > I believe we can ignore them now, I found the final dump and verified
> > it’s correct. Previously, I mistakenly halved the porch timings:
> >
> > Incorrect:
> > .hsync_total = (1280 + (32 + 12 + 38) / 2) * 2.
>
> If you halved the porches... Is this panel using a single DSI host or
> two DSI hosts? In the latter case you need to assign parents for DSI
> clocks (see how it's done on the sdm845-db845c)
>

Two dsi hosts. I was using your OOT patches for dual dsi cases until
you upstreamed them. So I have set

assigned-clock-parents = <&mdss_dsi0_phy DSI_BYTE_PLL_CLK>,
                         <&mdss_dsi0_phy DSI_PIXEL_PLL_CLK>;

as you did in your msm-next repo.

Best wishes,
Pengyu

  reply	other threads:[~2025-08-03  3:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17  9:29 [PATCH 0/4] arm64: dts: qcom: Introduce Ntmer TW220 Pengyu Luo
2025-06-17  9:29 ` [PATCH 1/4] dt-bindings: vendor-prefixes: Add Ntmer Pengyu Luo
2025-06-27 19:20   ` Rob Herring (Arm)
2025-06-17  9:29 ` [PATCH 2/4] dt-bindings: arm: qcom: Add Ntmer TW220 Pengyu Luo
2025-06-27 19:20   ` Rob Herring (Arm)
2025-06-17  9:29 ` [PATCH 3/4] arm64: dts: qcom: sc8280xp: Add initial support for " Pengyu Luo
2025-06-25  6:17   ` kernel test robot
2025-06-27 19:48   ` Konrad Dybcio
2025-07-06  3:43     ` Pengyu Luo
2025-07-30 12:53       ` Konrad Dybcio
2025-07-30 15:29         ` Pengyu Luo
2025-07-30 20:32           ` Konrad Dybcio
2025-07-31  3:05             ` Pengyu Luo
2025-08-01 12:29               ` Konrad Dybcio
2025-08-01 14:27                 ` Pengyu Luo
2025-08-01 17:27                   ` Dmitry Baryshkov
2025-08-03  3:36                     ` Pengyu Luo [this message]
2025-06-17  9:29 ` [PATCH 4/4] firmware: qcom: scm: Allow QSEECOM on " Pengyu Luo
2025-06-17 14:21 ` [PATCH 0/4] arm64: dts: qcom: Introduce " Rob Herring (Arm)

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=CAH2e8h6oN1VYevLe1NPpvcAjDjUNBrGUtEWy9y3pDhboCjabMA@mail.gmail.com \
    --to=mitltlatltl@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=ebiggers@google.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=joel.granados@kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=len.brown@intel.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=mingo@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=robh@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=vanyang@smail.nju.edu.cn \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).