From: Krzysztof Kozlowski <krzk@kernel.org>
To: jens.glathe@oldschoolsolutions.biz,
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,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v7 0/3] arm64: dts: qcom: x1-hp-x14: Add support for X1P42100 HP Omnibook X14
Date: Thu, 10 Jul 2025 12:53:34 +0200 [thread overview]
Message-ID: <553adfd2-8518-40b8-a762-1be026fb15b6@kernel.org> (raw)
In-Reply-To: <20250710-hp-x14-x1p-v7-0-19c10c81713a@oldschoolsolutions.biz>
On 10/07/2025 12:50, Jens Glathe via B4 Relay wrote:
> This patch series adds support for the HP Omnibook X Laptop 14-fe1xxx. [1]
>
> Since this is actually the same model as the 14-fe0xxx, but with an
> X1P-42-100 SoC (Purwa), it needs a slightly different device tree.
> To have as minimal duplicate definition as possible, the hp X14 gets
> commonalized into a dtsi (and it stays compatible to the derived
> device trees, like the Ultrabook G1q).
>
> The supported features are the same as for the original Omnibook X14:
>
> - Keyboard (no function keys though)
> - Display
> - PWM brightness control
> - Touchpad
> - Touchscreen
> - PCIe ports (pcie4, pcie6a)
> - USB type-c, type-a
> - WCN6855 Wifi-6E
> - WCN6855 Bluetooth
> - ADSP and CDSP
> - X1 GPU
> - GPIO Keys (Lid switch)
> - Audio definition (works via USB and with internal speakers)
>
> [1]: https://www.hp.com/us-en/shop/pdp/hp-omnibook-x-laptop-next-gen-ai-pc-14-fe100-14-a4nd1av-1#techSpecs
>
> Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
> ---
> Changes in v7:
> - rebased to next-20250710.
> - reworded commit message for patch #2
> - picked up reviewed-by for patch #3 (thanks)
> - fixed link ref in patch #3
> - Link to v6: https://lore.kernel.org/r/20250709-hp-x14-x1p-v6-0-f45cc186a62d@oldschoolsolutions.biz
Please slow down a bit. You keep sending every day. It is fine for
simple patchsets reaching v2 or v3... but this keeps going and you
reached v7!
Instead wait for few days to give people actually chance to review.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-10 10:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 10:50 Jens Glathe via B4 Relay
2025-07-10 10:50 ` [PATCH v7 1/3] dt-bindings: arm: qcom: Add HP Omnibook X14 AI X1P4200 variant Jens Glathe via B4 Relay
2025-07-10 10:50 ` [PATCH v7 2/3] arm64: dts: qcom: x1-hp-x14: Unify HP Omnibook X14 device tree structure Jens Glathe via B4 Relay
2025-07-10 10:55 ` Krzysztof Kozlowski
2025-07-10 11:31 ` Jens Glathe
2025-07-10 13:25 ` Krzysztof Kozlowski
2025-07-10 13:45 ` Jens Glathe
2025-07-10 12:31 ` Konrad Dybcio
2025-09-09 16:07 ` Bjorn Andersson
2025-09-13 17:46 ` Jens Glathe
2025-07-10 10:50 ` [PATCH v7 3/3] arm64: dts: qcom: x1-hp-x14: Add support for X1P42100 HP Omnibook X14 Jens Glathe via B4 Relay
2025-07-10 12:30 ` Konrad Dybcio
2025-07-10 10:53 ` Krzysztof Kozlowski [this message]
2025-09-16 16:58 ` [PATCH v7 0/3] " Bjorn Andersson
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=553adfd2-8518-40b8-a762-1be026fb15b6@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.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®