From: Frieder Hannenheim <mail@fhannenheim.net>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Frieder Hannenheim <git@fhannenheim.net>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: "Robert Oscilowski" <drgitx@gmail.com>,
"Jean-François Bobier" <jf.bobier@gmail.com>,
phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: oneplus-kebab: new device
Date: Fri, 16 Oct 2026 18:38:22 +0200 [thread overview]
Message-ID: <0ff136f5-5ed7-4fa0-a93a-07c06706273f@fhannenheim.net> (raw)
In-Reply-To: <c14fe062-2e87-4040-b9a8-7d90a04d7a8c@fhannenheim.net>
Hi Konrad, thanks for the review comments. Replies inline.
On 16.10.26 10:23, Konrad Dybcio wrote:
> On 10/15/26 2:32 PM, Frieder Hannenheim wrote:
>> Add initial device-tree for the OnePlus 8T. Downstream reference is [1].
>>
>> [1] https://github.com/LineageOS/android_kernel_oneplus_sm8250/blob/lineage-23.2/arch/arm64/boot/dts/vendor/oplus/kona-kebab-overlay.dts
>>
>> Signed-off-by: Frieder Hannenheim <git@fhannenheim.net>
>> Co-developed-by: Robert Oscilowski <drgitx@gmail.com>
>> Signed-off-by: Robert Oscilowski <drgitx@gmail.com>
>> ---
>> Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
>> arch/arm64/boot/dts/qcom/Makefile | 1 +
>> arch/arm64/boot/dts/qcom/sm8250-oneplus-kebab.dts | 129 ++++++++++++++++++++++
>
> Better. Please split off the dt-bindings changes to a separate patch,
> and put it first in the series.
>
> [...]
>
>
>> +&framebuffer {
>> + width = <1080>;
>> + height = <2400>;
>> + stride = <(1080 * 4)>;
>
> Does the resolution differ between the two devices?
There's 4 devices: 8 (instantnoodle), 8T (kebab), 8 Pro (instantnoodlep)
and 9R (lemonades).
All except the 8 Pro have a 2400x1080 screen, the 8 Pro has a 3168x1440
screen.
>
>> +};
>> +
>> +&i2c2 {
>> + status = "okay";
>> +
>> + pm8008: pmic@8 {
>> + compatible = "qcom,pm8008";
>
> Is it not present on the other one?
The OnePlus 8 doesn't have this according to the downstream dt. >> +
reg = <0x8>;
>> +
>> + interrupt-parent = <&tlmm>;
>> + interrupts = <112 IRQ_TYPE_EDGE_RISING>;
>> +
>> + reset-gpios = <&tlmm 93 GPIO_ACTIVE_LOW>;
>> +
>> + vdd-l1-l2-supply = <&vreg_s8c_1p3>;
>> + vdd-l3-l4-supply = <&vreg_bob>;
>> + vdd-l5-supply = <&vreg_bob>;
>> + vdd-l6-supply = <&vreg_bob>;
>> + vdd-l7-supply = <&vreg_bob>;
>> +
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&pm8008_default>, <&pm8008_interrupt>;
>
> nit:
>
> property-n
> property-names
>
> in this order, file-wide, please
Will fix
> [...]
>
>> +&i2c16 {
>> + status = "okay";
>> +
>> + fuel-gauge@55 {
>> + compatible = "ti,bq28z610";
>> + reg = <0x55>;
>> + monitored-battery = <&battery>;
>> + };
>
> Likewise, is this absent on the other phone?
Not absent but different. The 8T and 9R use two-cell batteries while the
others only have one cell and use a different fuel gauge.
>> +};
>> +
>> +&tlmm {
>> + pm8008_default: pm8008-default-state {
>> + pins = "gpio93";
>> + function = "gpio";
>> + bias-pull-up;
>> + output-high;
>
> Drop the output-high, the driver will set it for you
Will do.
Frieder
next parent reply other threads:[~2026-10-16 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c14fe062-2e87-4040-b9a8-7d90a04d7a8c@fhannenheim.net>
2026-10-16 16:38 ` Frieder Hannenheim [this message]
2026-10-15 12:32 [PATCH v2 0/2] Add OnePlus 8T Frieder Hannenheim
2026-10-15 12:32 ` [PATCH v2 2/2] arm64: dts: qcom: oneplus-kebab: new device Frieder Hannenheim
2026-10-16 8:23 ` Konrad Dybcio
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=0ff136f5-5ed7-4fa0-a93a-07c06706273f@fhannenheim.net \
--to=mail@fhannenheim.net \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=drgitx@gmail.com \
--cc=git@fhannenheim.net \
--cc=jf.bobier@gmail.com \
--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=phone-devel@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®