Messages in this thread |  | | Date | Mon, 7 Apr 2025 11:20:43 +0200 | | From | Juerg Haefliger <> | | Subject | Re: [PATCH 1/3] arm64: dts: qcom: x1e80100-hp-omnibook-x14: Create and include a dtsi |
| |
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
[unhandled content-type:application/pgp-signature] |  |