- Aarch64-laptops - lists.linaro.org

by Joshua Lee

Hello, this appears to be a development-only mailing list, so pardon me if I’m disturbing anyone. I’m running a Samsung Galaxy Book 2 (using SD850 + QUALCOMM x20 modem + AMOLED touch screen, detachable KB, and stylus) and am wondering if the work being done mostly on Lenovo SD850 laptops apparently and older devices will apply to this hardware, or should I not hold my breath? Don’t worry, this isn’t an ETA or a complaint, I appreciate everything you’re doing and wish I knew more about programming so I could help out. Sent from Mail for Windows 10

6 years, 11 months

2
1
0 0

blacklisting built-in and regular modules via cmdline instead of config

by Dimitri John Ledkov

So, we still have sensor-hub and acpi-button disabled using kernel config. I could patch the quirks into the kernel to skip loading those based on DMI data. However, that's a bit counter-productive as that's compiled in code and enumerates SKUs. Can I instead use kernel command line to skip initializing those built-in and compiled modules? Ie. would something like: module_blacklist=hid-sensor-hub initcall_blacklist=acpi_button_driver_init work, even when the kernel is configured with CONFIG_HID_SENSOR_HUB=m and CONFIG_ACPI_BUTTON=y ? Also not sure if I got the initcall function name right. I am asking because, it may be easier for me to control cmdline reliably, instead of distro kernel config. -- Regards, Dimitri.

6 years, 11 months

1
0
0 0

[PATCH 0/2] iommu: handle drivers that manage iommu directly

by Rob Clark

From: Rob Clark <robdclark(a)chromium.org> One of the challenges we need to handle to enable the aarch64 laptops upstream is dealing with the fact that the bootloader enables the display and takes the corresponding SMMU context-bank out of BYPASS. Unfortunately, currently, the IOMMU framework attaches a DMA (or potentially an IDENTITY) domain before the driver is probed and has a chance to intervene and shutdown[1] scanout. Which makes things go horribly wrong. This also happens to solve a problem that is blocking us from supporting per-context pagetables on the GPU, due to domain that is attached before driver has a chance to attach it's own domain for the GPU. But since the driver is managing it's own iommu domains directly, and does not use dev->iommu_group->default_domain at all, the simple solution to both problems is to just avoid attaching that domain in the first place. [1] Eventually we want to be able to do a seemless transition from efifb to drm/msm... but first step is to get the core (iommu, clk, genpd) pieces in place, so a first step of disabling the display before first modeset enables us to get all of the dependencies outside of drm/msm in place. And this at least gets us parity with windows (which also appears to do a modeset between bootloader and HLSO). After that there is a bunch of drm/msm work that is probably not interesting to folks outside of dri-devel. Rob Clark (2): iommu: add support for drivers that manage iommu explicitly drm/msm: mark devices where iommu is managed by driver drivers/gpu/drm/msm/adreno/adreno_device.c | 1 + drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 1 + drivers/gpu/drm/msm/disp/mdp5/mdp5_kms.c | 1 + drivers/gpu/drm/msm/msm_drv.c | 1 + drivers/iommu/iommu.c | 11 +++++++++++ include/linux/device.h | 3 ++- 6 files changed, 17 insertions(+), 1 deletion(-) -- 2.20.1

6 years, 11 months

4
15
0 0

Re: [Aarch64-laptops] [PATCH v8 3/5] arm64: dts: qcom: Add Lenovo Miix 630

by Dimitri John Ledkov

On Mon, 22 Jul 2019 at 20:33, Bjorn Andersson <bjorn.andersson(a)linaro.org> wrote: > > On Fri 21 Jun 07:54 PDT 2019, Jeffrey Hugo wrote: > > > This adds the initial DT for the Lenovo Miix 630 laptop. Supported > > functionality includes USB (host), microSD-card, keyboard, and trackpad. > > > > Signed-off-by: Jeffrey Hugo <jeffrey.l.hugo(a)gmail.com> > > Applied patch 3-5 > Sorry for a basic question, but which linux tree would one expect these to be applied in? I've poked a few obvious places, and don't see these applied. Also is Yoga C630 going to be submitted on top of these? Or should I submit them? Regards, Dimitri. > Thanks, > Bjorn > > > --- > > arch/arm64/boot/dts/qcom/Makefile | 1 + > > .../boot/dts/qcom/msm8998-clamshell.dtsi | 240 ++++++++++++++++++ > > .../boot/dts/qcom/msm8998-lenovo-miix-630.dts | 30 +++ > > 3 files changed, 271 insertions(+) > > create mode 100644 arch/arm64/boot/dts/qcom/msm8998-clamshell.dtsi > > create mode 100644 arch/arm64/boot/dts/qcom/msm8998-lenovo-miix-630.dts > > > > diff --git a/arch/arm64/boot/dts/qcom/Makefile b/arch/arm64/boot/dts/qcom/Makefile > > index 21d548f02d39..c3e4307bcbd4 100644 > > --- a/arch/arm64/boot/dts/qcom/Makefile > > +++ b/arch/arm64/boot/dts/qcom/Makefile > > @@ -6,6 +6,7 @@ dtb-$(CONFIG_ARCH_QCOM) += msm8916-mtp.dtb > > dtb-$(CONFIG_ARCH_QCOM) += msm8992-bullhead-rev-101.dtb > > dtb-$(CONFIG_ARCH_QCOM) += msm8994-angler-rev-101.dtb > > dtb-$(CONFIG_ARCH_QCOM) += msm8996-mtp.dtb > > +dtb-$(CONFIG_ARCH_QCOM) += msm8998-lenovo-miix-630.dtb > > dtb-$(CONFIG_ARCH_QCOM) += msm8998-mtp.dtb > > dtb-$(CONFIG_ARCH_QCOM) += sdm845-mtp.dtb > > dtb-$(CONFIG_ARCH_QCOM) += qcs404-evb-1000.dtb > > diff --git a/arch/arm64/boot/dts/qcom/msm8998-clamshell.dtsi b/arch/arm64/boot/dts/qcom/msm8998-clamshell.dtsi > > new file mode 100644 > > index 000000000000..9682d4dd7496 > > --- /dev/null > > +++ b/arch/arm64/boot/dts/qcom/msm8998-clamshell.dtsi > > @@ -0,0 +1,240 @@ > > +// SPDX-License-Identifier: GPL-2.0 > > +/* Copyright (c) 2019, Jeffrey Hugo. All rights reserved. */ > > + > > +/* > > + * Common include for MSM8998 clamshell devices, ie the Lenovo Miix 630, > > + * Asus NovaGo TP370QL, and HP Envy x2. All three devices are basically the > > + * same, with differences in peripherals. > > + */ > > + > > +#include "msm8998.dtsi" > > +#include "pm8998.dtsi" > > +#include "pm8005.dtsi" > > + > > +/ { > > + chosen { > > + }; > > + > > + vph_pwr: vph-pwr-regulator { > > + compatible = "regulator-fixed"; > > + regulator-name = "vph_pwr"; > > + regulator-always-on; > > + regulator-boot-on; > > + }; > > +}; > > + > > +&qusb2phy { > > + status = "okay"; > > + > > + vdda-pll-supply = <&vreg_l12a_1p8>; > > + vdda-phy-dpdm-supply = <&vreg_l24a_3p075>; > > +}; > > + > > +&rpm_requests { > > + pm8998-regulators { > > + compatible = "qcom,rpm-pm8998-regulators"; > > + > > + vdd_s1-supply = <&vph_pwr>; > > + vdd_s2-supply = <&vph_pwr>; > > + vdd_s3-supply = <&vph_pwr>; > > + vdd_s4-supply = <&vph_pwr>; > > + vdd_s5-supply = <&vph_pwr>; > > + vdd_s6-supply = <&vph_pwr>; > > + vdd_s7-supply = <&vph_pwr>; > > + vdd_s8-supply = <&vph_pwr>; > > + vdd_s9-supply = <&vph_pwr>; > > + vdd_s10-supply = <&vph_pwr>; > > + vdd_s11-supply = <&vph_pwr>; > > + vdd_s12-supply = <&vph_pwr>; > > + vdd_s13-supply = <&vph_pwr>; > > + vdd_l1_l27-supply = <&vreg_s7a_1p025>; > > + vdd_l2_l8_l17-supply = <&vreg_s3a_1p35>; > > + vdd_l3_l11-supply = <&vreg_s7a_1p025>; > > + vdd_l4_l5-supply = <&vreg_s7a_1p025>; > > + vdd_l6-supply = <&vreg_s5a_2p04>; > > + vdd_l7_l12_l14_l15-supply = <&vreg_s5a_2p04>; > > + vdd_l9-supply = <&vph_pwr>; > > + vdd_l10_l23_l25-supply = <&vph_pwr>; > > + vdd_l13_l19_l21-supply = <&vph_pwr>; > > + vdd_l16_l28-supply = <&vph_pwr>; > > + vdd_l18_l22-supply = <&vph_pwr>; > > + vdd_l20_l24-supply = <&vph_pwr>; > > + vdd_l26-supply = <&vreg_s3a_1p35>; > > + vdd_lvs1_lvs2-supply = <&vreg_s4a_1p8>; > > + > > + vreg_s3a_1p35: s3 { > > + regulator-min-microvolt = <1352000>; > > + regulator-max-microvolt = <1352000>; > > + }; > > + vreg_s4a_1p8: s4 { > > + regulator-min-microvolt = <1800000>; > > + regulator-max-microvolt = <1800000>; > > + regulator-allow-set-load; > > + }; > > + vreg_s5a_2p04: s5 { > > + regulator-min-microvolt = <1904000>; > > + regulator-max-microvolt = <2040000>; > > + }; > > + vreg_s7a_1p025: s7 { > > + regulator-min-microvolt = <900000>; > > + regulator-max-microvolt = <1028000>; > > + }; > > + vreg_l1a_0p875: l1 { > > + regulator-min-microvolt = <880000>; > > + regulator-max-microvolt = <880000>; > > + regulator-allow-set-load; > > + }; > > + vreg_l2a_1p2: l2 { > > + regulator-min-microvolt = <1200000>; > > + regulator-max-microvolt = <1200000>; > > + regulator-allow-set-load; > > + }; > > + vreg_l3a_1p0: l3 { > > + regulator-min-microvolt = <1000000>; > > + regulator-max-microvolt = <1000000>; > > + }; > > + vreg_l5a_0p8: l5 { > > + regulator-min-microvolt = <800000>; > > + regulator-max-microvolt = <800000>; > > + }; > > + vreg_l6a_1p8: l6 { > > + regulator-min-microvolt = <1808000>; > > + regulator-max-microvolt = <1808000>; > > + }; > > + vreg_l7a_1p8: l7 { > > + regulator-min-microvolt = <1800000>; > > + regulator-max-microvolt = <1800000>; > > + }; > > + vreg_l8a_1p2: l8 { > > + regulator-min-microvolt = <1200000>; > > + regulator-max-microvolt = <1200000>; > > + }; > > + vreg_l9a_1p8: l9 { > > + regulator-min-microvolt = <1808000>; > > + regulator-max-microvolt = <2960000>; > > + }; > > + vreg_l10a_1p8: l10 { > > + regulator-min-microvolt = <1808000>; > > + regulator-max-microvolt = <2960000>; > > + }; > > + vreg_l11a_1p0: l11 { > > + regulator-min-microvolt = <1000000>; > > + regulator-max-microvolt = <1000000>; > > + }; > > + vreg_l12a_1p8: l12 { > > + regulator-min-microvolt = <1800000>; > > + regulator-max-microvolt = <1800000>; > > + }; > > + vreg_l13a_2p95: l13 { > > + regulator-min-microvolt = <1808000>; > > + regulator-max-microvolt = <2960000>; > > + }; > > + vreg_l14a_1p88: l14 { > > + regulator-min-microvolt = <1880000>; > > + regulator-max-microvolt = <1880000>; > > + }; > > + vreg_15a_1p8: l15 { > > + regulator-min-microvolt = <1800000>; > > + regulator-max-microvolt = <1800000>; > > + }; > > + vreg_l16a_2p7: l16 { > > + regulator-min-microvolt = <2704000>; > > + regulator-max-microvolt = <2704000>; > > + }; > > + vreg_l17a_1p3: l17 { > > + regulator-min-microvolt = <1304000>; > > + regulator-max-microvolt = <1304000>; > > + }; > > + vreg_l18a_2p7: l18 { > > + regulator-min-microvolt = <2704000>; > > + regulator-max-microvolt = <2704000>; > > + }; > > + vreg_l19a_3p0: l19 { > > + regulator-min-microvolt = <3008000>; > > + regulator-max-microvolt = <3008000>; > > + }; > > + vreg_l20a_2p95: l20 { > > + regulator-min-microvolt = <2960000>; > > + regulator-max-microvolt = <2960000>; > > + regulator-allow-set-load; > > + }; > > + vreg_l21a_2p95: l21 { > > + regulator-min-microvolt = <2960000>; > > + regulator-max-microvolt = <2960000>; > > + regulator-allow-set-load; > > + regulator-system-load = <800000>; > > + }; > > + vreg_l22a_2p85: l22 { > > + regulator-min-microvolt = <2864000>; > > + regulator-max-microvolt = <2864000>; > > + }; > > + vreg_l23a_3p3: l23 { > > + regulator-min-microvolt = <3312000>; > > + regulator-max-microvolt = <3312000>; > > + }; > > + vreg_l24a_3p075: l24 { > > + regulator-min-microvolt = <3088000>; > > + regulator-max-microvolt = <3088000>; > > + }; > > + vreg_l25a_3p3: l25 { > > + regulator-min-microvolt = <3104000>; > > + regulator-max-microvolt = <3312000>; > > + }; > > + vreg_l26a_1p2: l26 { > > + regulator-min-microvolt = <1200000>; > > + regulator-max-microvolt = <1200000>; > > + }; > > + vreg_l28_3p0: l28 { > > + regulator-min-microvolt = <3008000>; > > + regulator-max-microvolt = <3008000>; > > + }; > > + > > + vreg_lvs1a_1p8: lvs1 { > > + regulator-min-microvolt = <1800000>; > > + regulator-max-microvolt = <1800000>; > > + }; > > + > > + vreg_lvs2a_1p8: lvs2 { > > + regulator-min-microvolt = <1800000>; > > + regulator-max-microvolt = <1800000>; > > + }; > > + > > + }; > > +}; > > + > > +&tlmm { > > + gpio-reserved-ranges = <0 4>, <81 4>; > > + > > + touchpad: touchpad { > > + config { > > + pins = "gpio123"; > > + bias-pull-up; /* pull up */ > > + }; > > + }; > > +}; > > + > > +&sdhc2 { > > + status = "okay"; > > + > > + vmmc-supply = <&vreg_l21a_2p95>; > > + vqmmc-supply = <&vreg_l13a_2p95>; > > + > > + pinctrl-names = "default", "sleep"; > > + pinctrl-0 = <&sdc2_clk_on &sdc2_cmd_on &sdc2_data_on &sdc2_cd_on>; > > + pinctrl-1 = <&sdc2_clk_off &sdc2_cmd_off &sdc2_data_off &sdc2_cd_off>; > > +}; > > + > > +&usb3 { > > + status = "okay"; > > +}; > > + > > +&usb3_dwc3 { > > + dr_mode = "host"; /* Force to host until we have Type-C hooked up */ > > +}; > > + > > +&usb3phy { > > + status = "okay"; > > + > > + vdda-phy-supply = <&vreg_l1a_0p875>; > > + vdda-pll-supply = <&vreg_l2a_1p2>; > > +}; > > diff --git a/arch/arm64/boot/dts/qcom/msm8998-lenovo-miix-630.dts b/arch/arm64/boot/dts/qcom/msm8998-lenovo-miix-630.dts > > new file mode 100644 > > index 000000000000..407c6a32911c > > --- /dev/null > > +++ b/arch/arm64/boot/dts/qcom/msm8998-lenovo-miix-630.dts > > @@ -0,0 +1,30 @@ > > +// SPDX-License-Identifier: GPL-2.0 > > +/* Copyright (c) 2019, Jeffrey Hugo. All rights reserved. */ > > + > > +/dts-v1/; > > + > > +#include "msm8998-clamshell.dtsi" > > + > > +/ { > > + model = "Lenovo Miix 630"; > > + compatible = "lenovo,miix-630", "qcom,msm8998"; > > +}; > > + > > +&blsp1_i2c6 { > > + status = "okay"; > > + > > + keyboard@3a { > > + compatible = "hid-over-i2c"; > > + interrupt-parent = <&tlmm>; > > + interrupts = <0x79 IRQ_TYPE_LEVEL_LOW>; > > + reg = <0x3a>; > > + hid-descr-addr = <0x0001>; > > + > > + pinctrl-names = "default"; > > + pinctrl-0 = <&touchpad>; > > + }; > > +}; > > + > > +&sdhc2 { > > + cd-gpios = <&tlmm 95 GPIO_ACTIVE_HIGH>; > > +}; > > -- > > 2.17.1 > > -- Regards, Dimitri.

6 years, 11 months

3
2
0 0

status: WW28 and WW29

by Richard Henwood

Hi All, I was on leave last week. I just chatted with Lee and have this summary of the last two weeks. + Tested on-disk install. + Update Windows to get latest firmware. + Disable 'S' mode and resize Windows partitions. + Boot up the Custom Ubuntu installer, and install. + With the latest windows firmware, most USB sticks work? + SanDisk looks problematic. + Reproduced and tested GPU stack. + Not working yet. + Believed to be a problem with an old Mesa version. + Rawhide doesn't boot to grub any more :( Blocking and Todo issues: + Hack to disable DMA in Qualcomm's Gini driver is still required + Kernel command-line: 'efi=novamap' required until f/w is fixed + CONFIG_HID_SENSOR_HUB still breaks the keyboard + CONFIG_ACPI_BUTTON places us into suspend with no real way out + Trying to get DTB into 5.3 kernel. best regards, Richard -- Richard.Henwood(a)arm.com Server Software Eco-System Tel: +1 512 410 9612 IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

6 years, 11 months

2
1
0 0

Network Support in ASUS NovaGo TP370QL

by Saravanan Somasundaram

Hi, I was able to follow the instructions in the following article and get Ubuntu booted successfully. https://github.com/aarch64-laptops/build#Flashing-the-image I understood that wireless network is not supported yet. If i plugin a USB Wii-Lan Adapter, the adapter is not recognized as well. Is there any other adapters that's known to work with ASUS Novago Laptop ? Thanks, Saravanan

6 years, 12 months

2
5
0 0

Re: [Aarch64-laptops] [PATCH v7 2/2] Add a module for retrieving SMBIOS information

by Dimitri John Ledkov

On Fri, 5 Jul 2019 at 13:48, David Michael <fedora.dm0(a)gmail.com> wrote: > > The following are two use cases from Rajat Jain <rajatjain(a)juniper.net>: > > 1) We have a board that boots Linux and this board itself can be plugged into one of different chassis types. We need to pass different parameters to the kernel based on the "CHASSIS_TYPE" information that is passed by the bios in the DMI / SMBIOS tables. > > 2) We may have a USB stick that can go into multiple boards, and the exact kernel to be loaded depends on the machine information (PRODUCT_NAME etc) passed via the DMI. > > Signed-off-by: David Michael <fedora.dm0(a)gmail.com> > Another use case is aarch64 laptops effort. We have the same kernel, and the same image bootable and usable across 4 different laptop models, with the only difference between them being the DTB to load. I was looking at how I can distinguish between the four models and automatically pick the right dtb. I did see these patches and was very sad when I found out that they didn't get merged. Thank you for rebasing these on top of v2.04. I will try to cherrypick them on top of Debian's experimental 2.04 grub and try to build an installer "that just boots" without requiring users to pick a particular dtb menuentry by hand. There are only dtbs in these images, and only one right one for each model. (Post install, we have flash-kernel mechanisms to continuously flash and use the right dtb, this is needed for the installer's grub to be able to detect models and thus boot the right dtb) Whilst these laptops might become dtb-free in the future, I expect new hardware to come out which would need dtb picker based on SMBIOS info again. -- Regards, Dimitri.

7 years

2
2
0 0

Firmware update (2.06) on c630

by Jason Allum

During a recent trip into windows-land, I noticed that Lenovo posted a firmware update for the c630. I downloaded and installed that, leaving my machine running 2.06. There don't appear to be any new menu options, and no description of the changes were available. I'm happy to run any diagnostic tooling for anyone that can't but is interested, if that information would be helpful to the cause.

7 years

1
0
0 0

laptop status and tasks: WW27

by Richard Henwood

Hi All, My notes from talking to Lee this week -------------------------------------- + DTB Loader v2.1 from Leif is available: http://git.linaro.org/people/leif.lindholm/edk2.git/log/?h=dtbloader + Allows dual boot Linux and Windows. + EBBR compliant. + Kernel command line options: + efi=novamap is required for DT and ACPI + This can only be fixed in firmware. + console=tty0, pd_ignore_unused, clk_ignore_unused + not required on both DT and ACPI + A Ubuntu kernel build with latest laptop patches is available: https://launchpad.net/~aarch64-laptops/+archive/ubuntu/linux-kernel/+build/… https://launchpad.net/~aarch64-laptops/+archive/ubuntu/linux-kernel-meta/+b… best regards, Richard -- Richard.Henwood(a)arm.com Server Software Eco-System IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

7 years

1
0
0 0

[PATCH 0/5] drm+clk+genpd: support for bootloader enabled display

by Rob Clark

From: Rob Clark <robdclark(a)chromium.org> The aarch64 laptops which ship with windows, have the display by the bootloader, and efifb (yah!). But unlike x86 laptops, device power management isn't handled via ACPI[1]. Currently the CCF and genpd frameworks will turn off power domains and clocks that they think are unused. This is rather unfortunate, as it kills efifb scanout before getting to userspace and getting to the point where we can try to probe the real display driver. Also it has a few side-effects in that we can't set rate on running clocks (in many cases). The first two patches let us flag clocks and power domains which might have been enabled by the bootloader, so we know not to disable them in late_initcall. The next two update drm/msm to cleanly shut down clocks which might already be running. *Eventually* we'll want to detect that scanout is already running, and readback the hw state, to avoid briefly disabling the screen while the driver loads. But that is a big pile of (mostly) drm/msm work. (Windows also seems to have this problem, it appears to do a modeset during boot.. so I guess the first step is to at least not suck more than windows ;-)) The last patch updates the bridge driver to handle the case where display is already active. (AFAICT it is the same bridge chip used so far on all the aarch64 laptops.) Because the bridge driver can be probed before the drm driver, and in fact you might end up with a bridge driver but no drm driver, care must be taken to not disable the bridge until the drm driver is ready to go, so: * Request enable gpio ASIS to avoid pulling down the enable gpio * Defer enabling runpm in the case that the bridge is already running until bridge->attach(). This is a point where we know the drm driver is ready to do a modeset. (There are a couple related cleanups in drm/msm to avoid touching the hw until we are past the point where we might -EPROBE_DEFER[2] which I sent seperately as they are probably interesting to fewer people.) This has been tested on a lenovo yoga c630. I've a wip/c630 branch[3] with this and various other work-in-progress stuff for this laptop. Next step, figuring out how to pick the proper panel driver, from the two or three possibilites that ship on this laptop ;-) [1] On windows, they use a "Platform Extension Plugin" (PEP) driver [2] https://patchwork.freedesktop.org/series/62999/ [3] https://github.com/freedreno/kernel-msm/commits/wip/c630 Rob Clark (5): clk: inherit clocks enabled by bootloader genpd/gdsc: inherit display powerdomain from bootloader drm/msm/dsi: split clk rate setting and enable drm/msm/dsi: get the clocks into OFF state at init drm/bridge: ti-sn65dsi86: support booloader enabled display drivers/base/power/domain.c | 10 ++++ drivers/clk/clk.c | 48 +++++++++++++++++++ drivers/clk/qcom/common.c | 25 ++++++++++ drivers/clk/qcom/dispcc-sdm845.c | 24 +++++----- drivers/clk/qcom/gcc-sdm845.c | 3 +- drivers/clk/qcom/gdsc.c | 5 ++ drivers/clk/qcom/gdsc.h | 1 + drivers/gpu/drm/bridge/ti-sn65dsi86.c | 12 ++++- drivers/gpu/drm/msm/dsi/dsi.h | 2 + drivers/gpu/drm/msm/dsi/dsi_cfg.c | 3 ++ drivers/gpu/drm/msm/dsi/dsi_cfg.h | 1 + drivers/gpu/drm/msm/dsi/dsi_host.c | 56 +++++++++++++++++----- drivers/gpu/drm/msm/dsi/pll/dsi_pll_10nm.c | 1 + include/linux/clk-provider.h | 10 ++++ include/linux/pm_domain.h | 4 ++ 15 files changed, 178 insertions(+), 27 deletions(-) -- 2.20.1

7 years

5
18
0 0

2026

2025

2024

2023

2022

2021

2020

2019

Aarch64-laptops