Message ID | 20250404090108.3333211-1-juerg.haefliger@canonical.com |
---|---|
Headers | show |
Series | HP EliteBook Ultra G1q support | expand |
On 04/04/2025 11:01, Juerg Haefliger wrote: > Create a dtsi for the HP OmniBook so it can be reused for the HP EliteBook > which seems to be the same HW. > > Signed-off-by: Juerg Haefliger <juerg.haefliger@canonical.com> > --- > .../dts/qcom/x1e80100-hp-omnibook-x14.dts | 1554 +--------------- > .../dts/qcom/x1e80100-hp-omnibook-x14.dtsi | 1557 +++++++++++++++++ > 2 files changed, 1558 insertions(+), 1553 deletions(-) > create mode 100644 arch/arm64/boot/dts/qcom/x1e80100-hp-omnibook-x14.dtsi Very difficult to review. This should have been rename. You are not using b4, so you can tweak -M/-B/-C parameters. I also do not understand what the DTSI represents. The DTSI files should be some sort of common hardware, design, product. Are you sure these devices share the design? Best regards, Krzysztof
On Fri, Apr 04, 2025 at 11:01:06AM +0200, Juerg Haefliger wrote: > Create a dtsi for the HP OmniBook so it can be reused for the HP EliteBook > which seems to be the same HW. > > Signed-off-by: Juerg Haefliger <juerg.haefliger@canonical.com> > --- > .../dts/qcom/x1e80100-hp-omnibook-x14.dts | 1554 +--------------- > .../dts/qcom/x1e80100-hp-omnibook-x14.dtsi | 1557 +++++++++++++++++ Just include x1e80100-hp-omnibook-x14.dts where you need it. There is no rule against including .dts files. Rob
On Fri, 4 Apr 2025 14:51:54 +0200 Krzysztof Kozlowski <krzk@kernel.org> wrote: > On 04/04/2025 11:01, Juerg Haefliger wrote: > > Create a dtsi for the HP OmniBook so it can be reused for the HP EliteBook > > which seems to be the same HW. > > > > Signed-off-by: Juerg Haefliger <juerg.haefliger@canonical.com> > > --- > > .../dts/qcom/x1e80100-hp-omnibook-x14.dts | 1554 +--------------- > > .../dts/qcom/x1e80100-hp-omnibook-x14.dtsi | 1557 +++++++++++++++++ > > 2 files changed, 1558 insertions(+), 1553 deletions(-) > > create mode 100644 arch/arm64/boot/dts/qcom/x1e80100-hp-omnibook-x14.dtsi > > Very difficult to review. This should have been rename. You are not > using b4, so you can tweak -M/-B/-C parameters. Not sure what that means, but OK :-) > > > I also do not understand what the DTSI represents. The DTSI files should > be some sort of common hardware, design, product. Are you sure these > devices share the design? Yes, pretty much. OmniBook: mainboard 8CBE, version 17.39 EliteBook: mainboard 8CBE, version 17.40 HWinfo from Windows looks identical. DSDT are identical except that the EliteBook has two additional nodes \_SB_.GPU0.PBRT.RBF5 and \_SB_.GPU0.PBRT.RBF6. Not sure what those are, maybe due to different BIOS versions? Using the current OmniBook dtb works with my EliteBook. ...Juerg > > Best regards, > Krzysztof
On Fri, 4 Apr 2025 10:33:39 -0500 Rob Herring <robh@kernel.org> wrote: > On Fri, Apr 04, 2025 at 11:01:06AM +0200, Juerg Haefliger wrote: > > Create a dtsi for the HP OmniBook so it can be reused for the HP EliteBook > > which seems to be the same HW. > > > > Signed-off-by: Juerg Haefliger <juerg.haefliger@canonical.com> > > --- > > .../dts/qcom/x1e80100-hp-omnibook-x14.dts | 1554 +--------------- > > .../dts/qcom/x1e80100-hp-omnibook-x14.dtsi | 1557 +++++++++++++++++ > > Just include x1e80100-hp-omnibook-x14.dts where you need it. There is no > rule against including .dts files. Ah that makes it easier. Thanks. ...Juerg > > Rob
On Tue, 08 Apr 2025 16:52:48 +0200, Juerg Haefliger wrote: > Add support for the HP EliteBook Ultra G1q 14" AI laptop. > > Based on HWINFO64 and APCI tables, it seems to be the same HW as the > HP OmniBook X 14. > > v1->v2: > - Don't rename the X14 dts to dtsi and directly include the dts > - Add a label to the sound node and use that to override the model > - Reorder the dt doc patch before the dt usage > > Juerg Haefliger (3): > arm64: dts: qcom: x1e80100-hp-omnibook-x14: add sound label and pull > out the model > dt-bindings: arm: qcom: Document HP EliteBook Ultra G1q > arm64: dts: qcom: x1e80100-hp-elitebook-ultra-g1q: DT for HP EliteBook > Ultra G1q > > .../devicetree/bindings/arm/qcom.yaml | 1 + > arch/arm64/boot/dts/qcom/Makefile | 1 + > .../qcom/x1e80100-hp-elitebook-ultra-g1q.dts | 36 +++++++++++++++++++ > .../dts/qcom/x1e80100-hp-omnibook-x14.dts | 7 ++-- > drivers/firmware/qcom/qcom_scm.c | 1 + > 5 files changed, 44 insertions(+), 2 deletions(-) > create mode 100644 arch/arm64/boot/dts/qcom/x1e80100-hp-elitebook-ultra-g1q.dts > > -- > 2.43.0 > > > My bot found new DTB warnings on the .dts files added or changed in this series. Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings are fixed by another series. Ultimately, it is up to the platform maintainer whether these warnings are acceptable or not. No need to reply unless the platform maintainer has comments. If you already ran DT checks and didn't see these error(s), then make sure dt-schema is up to date: pip3 install dtschema --upgrade This patch series was applied (using b4) to base: Base: attempting to guess base-commit... Base: tags/v6.15-rc1-3-gb09878285d23 (best guess, 1/4 blobs matched) If this is not the correct base, please add 'base-commit' tag (or use b4 which does this automatically) New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/qcom/' for 20250408145252.581060-1-juerg.haefliger@canonical.com: arch/arm64/boot/dts/qcom/x1e80100-hp-elitebook-ultra-g1q.dtb: pinctrl@f100000 (qcom,x1e80100-tlmm): Unevaluated properties are not allowed ('bt-en-sleep' was unexpected) from schema $id: http://devicetree.org/schemas/pinctrl/qcom,x1e80100-tlmm.yaml#