From: Val Packett <val@packett.cool>
To: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
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: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Add x1e Dell Inpsiron 14p
Date: Tue, 01 Jul 2025 18:48:07 -0300 [thread overview]
Message-ID: <266fdeb50ba3926a3edbda71201ffa021afecd62.camel@packett.cool> (raw)
In-Reply-To: <86116ada-51e6-4eef-bff1-f8b10a5edacc@gmail.com>
On Tue, 2025-07-01 at 22:43 +0200, Aleksandrs Vinarskis wrote:
>
> On 4/24/25 01:53, Bryan O'Donoghue wrote:
> > Add in a dtsi for the Dell Inspiron 14p.
> >
> > I'm currently using this as a daily driver including sending this
> > series
> > from. Its reasonably stable on 6.15-rcX.
> >
> > The first two patches can be applied without dependency, the final
> > patch
> > relies on patches staged for -next in the media tree to be applied,
> > presently.
> >
> > https://gitlab.freedesktop.org/linux-media/media-committers/-/commit/2ab7f87a7f4bf392e3836a2600f115a1baa1415c
> > https://lore.kernel.org/linux-media/20250407-b4-media-comitters-next-25-03-13-ov02e10-v4-0-211e3e6fae90@linaro.org/
> >
> > Working for me included in this series:
> >
> > - USB
> > Both Type-C USB ports
> > Type-A port
> > Fingerprint reader
> > - WiFi
> > - Bluetooth
> > - RGB Camera
> > - Toucpad, keyboard
> > - Display
> >
> > Working for me but not included:
> > - Audio jack
> > - Iris
> >
> > Not working:
> > - Speaker output
> > Still WiP haven't touched this in a while
> >
> > - Battery
> > Dell has its own Embedded Controller likely from the x86
> > platform reused
> > on Qcom which we need to reverse engineer or get some
> > information on to
> > make faster progress on.
> >
> > - cDSP
> > Haven't tried to bring this up.
> >
> > - EVA
> > No driver haven't tried it.
> >
> > - Bugs
> > Occasionally when resuming I get a fencing error with hyperlock
> > and
> > freedreno, TBH it looks like something in the GPU or SMMU
> > according to
> > Rob Clark: https://pastebin.com/AWjCyaap
> >
> > Ath12k has been splatting for me up to 6.14 when removing a
> > SSID.
> > I switched on ath12k debug when going to 6.15 and predictably
> > couldn't
> > reproduce the bug, either because the timings have changed as a
> > result
> > of Heisenbugging or because a fix has been slipped into ath12k.
> >
> > Other than those two I'm pretty happy with this system.
> >
> > The DTS is based on Aleksandrs Vinarskis XPS, Lenovo T14s and
> > Qcom CRD.
> >
> >
> > Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
>
> Hi,
>
> Just noticed that the device name is misspelled in a few occasions,
> need
> to s/inspirion/inspiron/. DT filename is wrong, model name in DT is
> wrong, one of commit messages is wrong. Firmware paths and compatible
> in
> DT are correct.
(BTW, in this submission in particular, firmware paths are not
consistent with existing models: the XPS uses lowercase 'dell')
> Otherwise, is the plan to wait for CAMSS to land, and then land this
> one, or perhaps the rest of it can go in already? There is also
> Latitude
> that was recently submitted which is very similar, perhaps those
> should
> be unified (CC: Val), probably easier to do if Inspiron lands first.
>
I have a unified patchset pretty much ready to go since yesterday.
With the way I have it, landing any one of the non-unified
submissions would only increase churn. I'll submit it now.
> Regards,
> Alex
>
> > ---
> > Bryan O'Donoghue (3):
> > dt-bindings: arm: qcom: Add Dell Inspiron 14 Plus 7441
> > arm64: dts: qcom: Add support for X1E80100 Dell Inspirion 14
> > Plus 7441
> > arm64: dts: qcom: x1e80100-dell-inspiron14-7441: Switch on
> > CAMSS RGB sensor
> >
> > Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
> > arch/arm64/boot/dts/qcom/Makefile | 1 +
> > .../qcom/x1e80100-dell-inspirion-14-plus-7441.dts | 1490
> > ++++++++++++++++++++
> > 3 files changed, 1492 insertions(+)
> > ---
> > base-commit: f7570505263aff2b63142f0d68fa607cd60eb060
> > change-id: 20250417-qcom-linux-arm64-for-6-16-dell-inspiron14p-
> > ed68cd65ebad
> >
> > Best regards,
next prev parent reply other threads:[~2025-07-01 21:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 23:53 Bryan O'Donoghue
2025-04-23 23:53 ` [PATCH 1/3] dt-bindings: arm: qcom: Add Dell Inspiron 14 Plus 7441 Bryan O'Donoghue
2025-04-28 8:24 ` Krzysztof Kozlowski
2025-04-23 23:53 ` [PATCH 2/3] arm64: dts: qcom: Add support for X1E80100 Dell Inspirion " Bryan O'Donoghue
2025-04-25 20:06 ` Konrad Dybcio
2025-07-11 19:38 ` Laurentiu Tudor
2025-04-23 23:53 ` [PATCH 3/3] arm64: dts: qcom: x1e80100-dell-inspiron14-7441: Switch on CAMSS RGB sensor Bryan O'Donoghue
2025-04-24 15:42 ` [PATCH 0/3] Add x1e Dell Inpsiron 14p Rob Clark
2025-04-24 15:45 ` Bryan O'Donoghue
2025-07-01 20:43 ` Aleksandrs Vinarskis
2025-07-01 21:48 ` Val Packett [this message]
2025-07-01 22:04 ` Aleksandrs Vinarskis
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=266fdeb50ba3926a3edbda71201ffa021afecd62.camel@packett.cool \
--to=val@packett.cool \
--cc=alex.vinarskis@gmail.com \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.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=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®