From: Catherine Frederick <serenity@floorchan.org>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Catherine Frederick <serenity@floorchan.org>,
linux-clk@vger.kernel.org
Subject: Fwd: [PATCH v2 0/3] arm64: dts: qcom: initial MSM8920 and Motorola Moto E4 (perry)
Date: Thu, 23 Jul 2026 14:07:06 -0400 [thread overview]
Message-ID: <247df8ea-49c7-46e4-acfc-e56d0ad9f8ed@floorchan.org> (raw)
In-Reply-To: <4006f966cd5f0c077c413410d79bae1e@floorchan.org>
Forwarding to everyone on the list, since this didn't make it there
(Damn you roundcube!). A lot of the errors in this PR are results of
Claude mindlessly copy-pasting my in-progress work (bad whitespace,
incorrect copyright assignments). Fuck man. Sorry in advance if my email
client makes a mess on the list.
-------- Forwarded Message --------
Subject: Re: [PATCH v2 0/3] arm64: dts: qcom: initial MSM8920 and
Motorola Moto E4 (perry)
Date: Thu, 23 Jul 2026 08:49:25 -0400
From: serenity@floorchan.org
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
On 2026-07-23 08:00, Konrad Dybcio wrote:
> On 7/23/26 3:46 AM, Aneesh Pradhan wrote:
>> Initial upstream support for MSM8920 and the Motorola Moto E4 (perry).
>>
>> Depends on the separate qcom,rpmcc-msm8920 clk series (binding +
>> clk-smd-rpm) for the MSM8920 rpmcc compatible used by msm8920.dtsi.
>>
>> This is a trimmed mainline-first subset of msm89x7-mainline/linux#48,
>> rewritten so every phandle exists on qcom/for-next's msm8917 / pm8937 /
>> pmi8950 (the fork DT assumed richer SoC/PMIC nodes that are not
>> upstream yet).
>>
>> Included: regulators, eMMC/SD, USB OTG (gpio-id extcon), keys, RMI4
>> touch + reset-gpios, BMA253 (i2c-gpio), WCNSS (wcn3660b), PMI8950 WLED.
>> Deferred follow-ups: DSI panel, IPA, QDSP6 audio, FG/smbcharger, modem.
>>
>> DTB build verified: msm8917-motorola-perry.dtb +
>> msm8920-motorola-perry.dtb.
>
> Please send all series as separate threads and all revisions as separate
> threads too. You can use the b4 tool [1] which takes care of that and a
> couple other annoyances
>
> Konrad
>
> [1] https://b4.docs.kernel.org/en/latest/
Hi,
I just wanted to let you know, this is a drive-by-vibe rendition of my
patch series from earlier this year. You aren't talking to a person, but
claude code instead:
https://github.com/aneesh-pradhan/xylitol/commit/4bdb6eaac4724ae0071095a925795c5e5b8b9985
I can confirm both the MSM8917 and MSM8920 variants exist in the wild,
as I own both. As for what you want to do with all this information,
that's up to you. This also contains hacked up versions of my in
progress DT for perry available on the msm89x7-mainline git. I was
planning on picking up this series when I had time again.
Thanks,
Catherine
parent reply other threads:[~2026-07-23 18:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4006f966cd5f0c077c413410d79bae1e@floorchan.org>]
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=247df8ea-49c7-46e4-acfc-e56d0ad9f8ed@floorchan.org \
--to=serenity@floorchan.org \
--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-clk@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