From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Paul Adam <adamp@posteo.de>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: qcom: msm8916-wiko-chuppito: add initial devicetree
Date: Tue, 17 Feb 2026 12:04:44 +0100 [thread overview]
Message-ID: <b6642f5e-c890-42fd-a733-c5ff1cc95d25@oss.qualcomm.com> (raw)
In-Reply-To: <aZRJb6FVi6B-fgWF@MyryksLaptop>
On 2/17/26 11:57 AM, Paul Adam wrote:
> On 26/02/16 12:18, Konrad Dybcio wrote:
>> Hello, just a couple comments below
>
> Thanks for the feedback!
>
>>> +// make sure gcc is probed with display disabled.
>>> +&gcc {
>>> + clocks = <&xo_board>, <&sleep_clk>, <0>, <0>, <0>, <0>, <0>;
>>> +};
>>
>> Do things break if you remove this line?
>
> I tested it without and it still works. I just included it because
> it was on the pmos msm8916 mainlining wiki page.
If nothing breaks, let's remove it :)
>>> +
>>> +&gpu {
>>> + status = "okay";
>>> +};
>>> +
>>> +&mdss {
>>> + status = "okay";
>>> +};
>>> +
>>> +&mpss_mem {
>>> + reg = <0x0 0x86800000 0x0 0x5600000>;
>>> +};
>>> +
>>> +&pm8916_l6 {
>>> + regulator-always-on;
>>
>> Is there a reason for this?
>
> I removed the always-on property, it was for testing purposes.
> mpss_mem is needed for audio to work.
> I removed mdss since it is only needed for the panel.
> Should the gpu only be enabled when the panel is added?
Ah, I only meant the regulator-always-on part specifically
The rest is OK, including the GPU and MDSS
> Also should I wait some time for additional comments or immediatly
> send a new version when all remarks are addressed?
Normally one would wait some 2-3 days after sending. Because we're now in
the special part of the cycle (post stable release, pre -rc1 release where no
new patches are accepted yet), some people will be grumpy and actively refuse
to review your changes but I wouldn't pay too much attention to that
Konrad
prev parent reply other threads:[~2026-02-17 11:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-15 20:02 [PATCH 0/3] Add wiko-chuppito devictree Paul Adam via B4 Relay
2026-02-15 20:02 ` [PATCH 1/3] dt-bindings: vendor-prefixes: add WIKO SAS Paul Adam via B4 Relay
2026-02-16 7:35 ` Krzysztof Kozlowski
2026-02-15 20:02 ` [PATCH 2/3] dt-bindings: arm: qcom: add wiko,chuppito compatible string Paul Adam via B4 Relay
2026-02-15 20:02 ` [PATCH 3/3] arm64: dts: qcom: msm8916-wiko-chuppito: add initial devicetree Paul Adam via B4 Relay
2026-02-16 11:18 ` Konrad Dybcio
2026-02-17 10:57 ` Paul Adam
2026-02-17 11:04 ` 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=b6642f5e-c890-42fd-a733-c5ff1cc95d25@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=adamp@posteo.de \
--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=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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®