lp:~ubuntu-concept/ubuntu/+source/linux/+git/oracular

Owned by Ubuntu Concept
Get this repository:
git clone https://git.launchpad.net/~ubuntu-concept/ubuntu/+source/linux/+git/oracular
Members of Ubuntu Concept can upload to this repository. Log in for directions.

Branches

Name Last Modified Last Commit
qcom-x1e 2025-05-07 23:10:51 UTC
Changelog for 6.14.0-34.34

Author: Tobias Heider
Author Date: 2025-05-07 13:28:57 UTC

Changelog for 6.14.0-34.34

ubuntu/plucky-x1e 2025-03-14 10:30:24 UTC
UBUNTU: [Config] Enable X Elite modules on arm64

Author: Tobias Heider
Author Date: 2025-03-13 11:31:29 UTC

UBUNTU: [Config] Enable X Elite modules on arm64

BugLink: https://bugs.launchpad.net/bugs/2100858

ps883x and Yoga Slim EC are required on X Elite laptops.

Signed-off-by: Tobias Heider <tobias.heider@canonical.com>

unstable-x1e 2025-03-13 22:24:26 UTC
UBUNTU: SAUCE: hack: efi/libstub: mitigate t14s exit_boot_services() failure

Author: Johan Hovold
Author Date: 2024-11-27 15:05:37 UTC

UBUNTU: SAUCE: hack: efi/libstub: mitigate t14s exit_boot_services() failure

BugLink: https://bugs.launchpad.net/bugs/2100858

The UEFI firmware on the Lenovo ThinkPad T14s is broken and
ExitBootServices() often fails and prevents the kernel from starting:

 EFI stub: Exiting boot services...
 EFI stub: Exit boot services failed.

One bootloader entry may fail to start almost consistently (once in a
while it may start), while a second entry may always work even when the
kernel, dtb and initramfs images are copies of the failing entry on the
same ESP.

This can be worked around by starting and exiting a UEFI shell from the
bootloader or by starting the bootloader manually via the Boot Menu
(F12) before starting the kernel.

Notably starting the kernel automatically from the shell startup.nsh
does not work, while calling the same script manually works.

Experiments have revealed that allocating an event before calling
ExitBootServices() can make the call succeed. When providing a
notification function there apparently is no need to actually signal the
event group and CloseEvent() could also be called directly.

Loading the initramfs and dtb from the EFI stub (using the 'initrd' and
'dtb' kernel parameters) instead of from the bootloader can also reduce
the chances of hitting this bug.

Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
(cherry picked from commit 7aad6a51917e7914a7a6d00b8e3f7999da542627 github.com/jhovold/linux)
Signed-off-by: Tobias Heider <tobias.heider@canonical.com>

ubuntu/unstable-x1e 2025-03-10 13:56:28 UTC
UBUNTU: SAUCE: arm64: dts: qcom: x1e80100-dell-xps-9345: Add WiFi/BT pwrseq

Author: alex
Author Date: 2025-03-09 15:47:02 UTC

UBUNTU: SAUCE: arm64: dts: qcom: x1e80100-dell-xps-9345: Add WiFi/BT pwrseq

Add the WiFi/BT nodes for XPS and describe the regulators for the WCN7850
combo chip using the new power sequencing bindings. All voltages are
derived from chained fixed regulators controlled using a single GPIO.

Derived from:
arm64: dts: qcom: x1e80100-qcp: Add WiFi/BT pwrseq

Signed-off-by: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>
Signed-off-by: Tobias Heider <tobias.heider@canonical.com>

qcom-x1e-6.14 2025-03-08 00:31:09 UTC
UBUNTU: Changelog for 6.14.0-20.20

Author: Tobias Heider
Author Date: 2025-03-08 00:31:09 UTC

UBUNTU: Changelog for 6.14.0-20.20

x1e-6.14/900-packaging 2025-02-27 16:41:52 UTC
UBUNTU: Changelog for 6.14.0-15.15

Author: Tobias Heider
Author Date: 2025-02-27 13:08:30 UTC

UBUNTU: Changelog for 6.14.0-15.15

x1e-6.14/203-yoga-slim 2025-02-27 16:35:15 UTC
arm64: dts: qcom: Add EC to Lenovo Yoga Slim 7x

Author: Maya Matuszczyk
Author Date: 2024-09-27 18:53:42 UTC

arm64: dts: qcom: Add EC to Lenovo Yoga Slim 7x

This device has an EC on i2c5 bus at address 0x76, driver for the EC was
added in a previous patch.

Signed-off-by: Maya Matuszczyk <maccraft123mc@gmail.com>
Reviewed-by: Konrad Dybcio <konradybcio@kernel.org>

x1e-6.14/110-x1e80100 2025-02-27 13:00:08 UTC
arm64: dts: qcom: x1e80100: Add crypto engine

Author: Abel Vesa
Author Date: 2025-02-21 13:07:03 UTC

arm64: dts: qcom: x1e80100: Add crypto engine

On X Elite, there is a crypto engine IP block similar to ones found on
SM8x50 platforms.

Describe the crypto engine and its BAM.

Signed-off-by: Abel Vesa <abel.vesa@linaro.org>

x1e-6.14/430-iris 2025-02-24 14:14:53 UTC
arm64: defconfig: Enable IRIS video codec

Author: Stephan Gerhold
Author Date: 2024-08-08 09:21:25 UTC

arm64: defconfig: Enable IRIS video codec

x1e-6.14/410-audio 2025-02-24 14:13:00 UTC
UBUNTU: Audio support on X Elite is currently experimental and comes

Author: Tobias Heider
Author Date: 2024-12-10 12:04:28 UTC

UBUNTU: Audio support on X Elite is currently experimental and comes
with a risk of permanently damaging hardware. Add an explicit kernel
command line flag to make sure it doesn't get enabled by accident.

x1e-6.14/420-efi 2025-02-24 14:12:17 UTC
hack: efi/libstub: fix t14s exit_boot_services() failure

Author: Johan Hovold
Author Date: 2024-11-28 08:20:36 UTC

hack: efi/libstub: fix t14s exit_boot_services() failure

The UEFI firmware on the Lenovo ThinkPad T14s is broken and
ExitBootServices() often fails and prevents the kernel from starting:

 EFI stub: Exiting boot services...
 EFI stub: Exit boot services failed.

One bootloader entry may fail to start almost consistently (once in a
while it may start), while a second entry may always work even when the
kernel, dtb and initramfs images are copies of the failing entry on the
same ESP.

This can be worked around by starting and exiting a UEFI shell from the
bootloader or by starting the bootloader manually via the Boot Menu
(F12) before starting the kernel.

Notably starting the kernel automatically from the shell startup.nsh
does not work, while calling the same script manually works.

Experiments have revealed that allocating an event before calling
ExitBootServices() can make the call succeed. There is often no need to
actually signal the event group, but the event must remain allocated
(i.e. CloseEvent() must not be called).

Also with the event signalling, ExitBootServices() sometimes fails when
starting the kernel automatically from a shell startup.nsh, while
systemd-boot seems to always work. This was only observed after removing
some efi_printk() used during the experiments from the stub...

Signed-off-by: Johan Hovold <johan+linaro@kernel.org>

x1e-6.14/400-drm 2025-02-24 14:09:35 UTC
drm/msm/dp: Add support for LTTPR handling

Author: Abel Vesa
Author Date: 2025-01-03 12:58:18 UTC

drm/msm/dp: Add support for LTTPR handling

Link Training Tunable PHY Repeaters (LTTPRs) are defined in DisplayPort
1.4a specification. As the name suggests, these PHY repeaters are
capable of adjusting their output for link training purposes.

According to the DisplayPort standard, LTTPRs have two operating
modes:
 - non-transparent - it replies to DPCD LTTPR field specific AUX
   requests, while passes through all other AUX requests
 - transparent - it passes through all AUX requests.

Switching between this two modes is done by the DPTX by issuing
an AUX write to the DPCD PHY_REPEATER_MODE register.

The msm DP driver is currently lacking any handling of LTTPRs.
This means that if at least one LTTPR is found between DPTX and DPRX,
the link training would fail if that LTTPR was not already configured
in transparent mode.

The section 3.6.6.1 from the DisplayPort v2.0 specification mandates
that before link training with the LTTPR is started, the DPTX may place
the LTTPR in non-transparent mode by first switching to transparent mode
and then to non-transparent mode. This operation seems to be needed only
on first link training and doesn't need to be done again until device is
unplugged.

It has been observed on a few X Elite-based platforms which have
such LTTPRs in their board design that the DPTX needs to follow the
procedure described above in order for the link training to be successful.

So add support for reading the LTTPR DPCD caps to figure out the number
of such LTTPRs first. Then, for platforms (or Type-C dongles) that have
at least one such an LTTPR, set its operation mode to transparent mode
first and then to non-transparent, just like the mentioned section of
the specification mandates.

Tested-by: Johan Hovold <johan+linaro@kernel.org>
Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Reviewed-by: Johan Hovold <johan+linaro@kernel.org>

x1e-6.14/210-devkit 2025-02-24 13:22:54 UTC
arm64: dts: qcom: x1e001de-devkit: Set ps8830 reset-gpios active low

Author: Tobias Heider
Author Date: 2025-02-24 13:07:07 UTC

arm64: dts: qcom: x1e001de-devkit: Set ps8830 reset-gpios active low

x1e-6.14/207-acer-swift-sf14-11 2025-02-24 13:22:25 UTC
firmware: qcom: scm: Allow QSEECOM on Acer Swift 14 models

Author: Tobias Heider
Author Date: 2025-02-06 15:34:15 UTC

firmware: qcom: scm: Allow QSEECOM on Acer Swift 14 models

Add the aforementioned machines to the list to get e.g. efivars up.

x1e-6.14/206-asus-vivobook 2025-02-24 13:21:49 UTC
arm64: dts: qcom: x1e80100-vivobook-s15: Enable HBR3 on external DPs

Author: alex
Author Date: 2024-12-28 21:40:40 UTC

arm64: dts: qcom: x1e80100-vivobook-s15: Enable HBR3 on external DPs

When no link frequencies are set, msm/dp driver defaults to HBR2 speed.
Explicitly list supported frequencies including HBR3/8.1Gbps for all
external DisplayPort(s).

Signed-off-by: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>

x1e-6.14/205-hp-omnibook 2025-02-24 13:20:48 UTC
arm64: dts: qcom: x1e80100-hp-x14: Enable HBR3 on external DPs

Author: alex
Author Date: 2024-12-28 21:35:15 UTC

arm64: dts: qcom: x1e80100-hp-x14: Enable HBR3 on external DPs

When no link frequencies are set, msm/dp driver defaults to HBR2 speed.
Explicitly list supported frequencies including HBR3/8.1Gbps for all
external DisplayPort(s).

Signed-off-by: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>

x1e-6.14/201-dell-xps 2025-02-24 13:19:05 UTC
arm64: dts: qcom: x1e80100-dell-xps13-9345: Enable HBR3 on external DPs

Author: alex
Author Date: 2024-12-28 17:46:50 UTC

arm64: dts: qcom: x1e80100-dell-xps13-9345: Enable HBR3 on external DPs

When no link frequencies are set, msm/dp driver defaults to HBR2 speed.
Explicitly list supported frequencies including HBR3/8.1Gbps for all
external DisplayPort(s).

Signed-off-by: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>

x1e-6.14/200-t14s 2025-02-24 13:18:31 UTC
arm64: dts: qcom: x1e78100-lenovo-thinkpad-t14s: Add bluetooth

Author: Tobias Heider
Author Date: 2024-10-23 12:58:31 UTC

arm64: dts: qcom: x1e78100-lenovo-thinkpad-t14s: Add bluetooth

Signed-off-by: Tobias Heider <tobias.heider@canonical.com>

x1e-6.14/100-next 2025-02-24 12:07:10 UTC
usb: typec: ps883x: fix configuration error handling

Author: Johan Hovold
Author Date: 2025-02-18 14:43:15 UTC

usb: typec: ps883x: fix configuration error handling

Propagate errors to the consumers when configuring the retimer so that
they can act on any failures as intended, for example:

 ps883x_retimer 2-0008: failed to write conn_status_0: -5
 pmic_glink_altmode.pmic_glink_altmode pmic_glink.altmode.0: failed to setup retimer to DP: -5

Fixes: 257a087c8b52 ("usb: typec: Add support for Parade PS8830 Type-C Retimer")
Cc: Abel Vesa <abel.vesa@linaro.org>
Signed-off-by: Johan Hovold <johan+linaro@kernel.org>

x1e-6.14/208-honor-magicbook-art-14 2025-02-14 12:10:39 UTC
arm64: dts: qcom: x1e80100: add HONOR MagicBook Art 14 devicetree

Author: Kirill A. Korinskiy
Author Date: 2025-01-12 17:19:58 UTC

arm64: dts: qcom: x1e80100: add HONOR MagicBook Art 14 devicetree

Introduce device tree for the HONOR MagicBook Art 14, built on the
Qualcomm Snapdragon X Elite SoC (X1E78100).

Supported features:

- Keyboard
- Display
- Touchpad
- Touchscreen
- PCIe ports (pcie4)
- USB type-c, type-a, Magnetic webcam connector
- Wifi (WCN7850)
- ADSP and CDSP
- X1 GPU
- GPIO Keys (Lid switch)
- Audio definition
- UFS storage

Signed-off-by: Kirill A. Korinsky <kirill@korins.ky>

x1e-6.14/204-galaxy-book 2025-02-14 11:55:19 UTC
firmware: qcom: scm: Allow QSEECOM on Samsung Galaxy Book4 Edge

Author: Tobias Heider
Author Date: 2024-10-18 04:07:40 UTC

firmware: qcom: scm: Allow QSEECOM on Samsung Galaxy Book4 Edge

Signed-off-by: Tobias Heider <tobias.heider@canonical.com>

qcom-x1e-6.13 2025-02-12 10:17:54 UTC
UBUNTU: Changelog for 6.13.0-4.4

Author: Tobias Heider
Author Date: 2025-02-12 10:17:54 UTC

UBUNTU: Changelog for 6.13.0-4.4

x1e-6.13/110-x1e80100 2025-02-11 14:23:58 UTC
platform: arm64: Add driver for EC found in most X1E laptops

Author: Maya Matuszczyk
Author Date: 2024-12-19 20:08:19 UTC

platform: arm64: Add driver for EC found in most X1E laptops

Currently it features only reporting that the AP is going to suspend,
which results in keyboard backlight turning off and the power LED
slowly blinking on the Lenovo Yoga Slim 7x.

Honor Magicbook Art 14 and Lenovo Yoga Slim 7x are known to have
firmware with extensions which would need appropriate handling.
For reverse engineering the firmware on them I have written a Rust
utility:

https://github.com/Maccraft123/it8987-qcom-tool.git

Signed-off-by: Maya Matuszczyk <maccraft123mc@gmail.com>

x1e-6.12/900-packaging 2025-02-06 16:09:26 UTC
UBUNTU: Changelog for 6.12.0-28.28

Author: Tobias Heider
Author Date: 2025-01-24 00:12:26 UTC

UBUNTU: Changelog for 6.12.0-28.28

x1e-6.12/207-acer-swift-sf14-11 2025-02-06 15:34:15 UTC
firmware: qcom: scm: Allow QSEECOM on Acer Swift 14 models

Author: Tobias Heider
Author Date: 2025-02-06 15:34:15 UTC

firmware: qcom: scm: Allow QSEECOM on Acer Swift 14 models

Add the aforementioned machines to the list to get e.g. efivars up.

x1e-6.12/208-honor-magicbook-art-14 2025-01-23 18:32:22 UTC
arm64: dts: qcom: x1e80100: add HONOR MagicBook Art 14 devicetree

Author: Kirill A. Korinskiy
Author Date: 2025-01-12 17:19:58 UTC

arm64: dts: qcom: x1e80100: add HONOR MagicBook Art 14 devicetree

Introduce device tree for the HONOR MagicBook Art 14, built on the
Qualcomm Snapdragon X Elite SoC (X1E78100).

Supported features:

- Keyboard
- Display
- Touchpad
- Touchscreen
- PCIe ports (pcie4)
- USB type-c, type-a, Magnetic webcam connector
- Wifi (WCN7850)
- ADSP and CDSP
- X1 GPU
- GPIO Keys (Lid switch)
- Audio definition
- UFS storage

Signed-off-by: Kirill A. Korinsky <kirill@korins.ky>

x1e-6.12/200-t14s 2025-01-23 00:36:41 UTC
arm64: dts: qcom: x1e78100-t14s: Enable fingerprint reader

Author: Abel Vesa
Author Date: 2025-01-07 13:35:07 UTC

arm64: dts: qcom: x1e78100-t14s: Enable fingerprint reader

On Lenovo ThinkPad T14s, the fingerprint reader placed in the power
button is connected via the usb_2 controller. The controller has only
a USB 2.0 PHY which is then connected via a NXP PTN3222 eUSB2 repeater,
which in turn is connected to the Goodix fingerprint reader.

So enable all the usb_2 controller and PHY nodes, set dual-role mode to
host and describe the eUSB2 repeater in order to get the fingerprint
reader discovered.

Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
Reviewed-by: Johan Hovold <johan+linaro@kernel.org>
Tested-by: Johan Hovold <johan+linaro@kernel.org>

x1e-6.12/110-x1e80100 2025-01-22 22:28:55 UTC
arm64: dts: qcom: x1e80100: enable rtc

Author: Johan Hovold
Author Date: 2025-01-20 14:41:52 UTC

arm64: dts: qcom: x1e80100: enable rtc

On many Qualcomm platforms the PMIC RTC control and time registers are
read-only so that the RTC time can not be updated. Instead an offset
needs be stored in some machine-specific non-volatile memory, which a
driver can take into account.

On X1E based Windows on Arm machines the offset is stored in a Qualcomm
specific UEFI variable.

Unlike on previous platforms the alarm registers are also unaccessible
on X1E as they are owned by the ADSP.

Assume all X1E machines use similar firmware and enable the RTC in the
PMIC dtsi for now.

Based on a patch by Jonathan Marek. [1]

Link: https://lore.kernel.org/r/20241015004945.3676-4-jonathan@marek.ca # [1]
Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
Tested-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Tested-by: Steev Klimaszewski <steev@kali.org>
Tested-by: Joel Stanley <joel@jms.id.au>

x1e-6.12/210-devkit 2024-12-28 21:58:34 UTC
arm64: dts: qcom: x1e001de-devkit: Enable HBR3 on external DPs

Author: alex
Author Date: 2024-12-28 21:58:34 UTC

arm64: dts: qcom: x1e001de-devkit: Enable HBR3 on external DPs

When no link frequencies are set, msm/dp driver defaults to HBR2 speed.
Explicitly list supported frequencies including HBR3/8.1Gbps for all
external DisplayPort(s).

Signed-off-by: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>

x1e-6.12/206-asus-vivobook 2024-12-28 21:40:40 UTC
arm64: dts: qcom: x1e80100-vivobook-s15: Enable HBR3 on external DPs

Author: alex
Author Date: 2024-12-28 21:40:40 UTC

arm64: dts: qcom: x1e80100-vivobook-s15: Enable HBR3 on external DPs

When no link frequencies are set, msm/dp driver defaults to HBR2 speed.
Explicitly list supported frequencies including HBR3/8.1Gbps for all
external DisplayPort(s).

Signed-off-by: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>

x1e-6.12/205-hp-omnibook 2024-12-28 21:35:15 UTC
arm64: dts: qcom: x1e80100-hp-x14: Enable HBR3 on external DPs

Author: alex
Author Date: 2024-12-28 21:35:15 UTC

arm64: dts: qcom: x1e80100-hp-x14: Enable HBR3 on external DPs

When no link frequencies are set, msm/dp driver defaults to HBR2 speed.
Explicitly list supported frequencies including HBR3/8.1Gbps for all
external DisplayPort(s).

Signed-off-by: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>

x1e-6.12/201-dell-xps 2024-12-28 21:05:55 UTC
arm64: dts: qcom: x1e80100-dell-xps13-9345: Enable HBR3 on external DPs

Author: alex
Author Date: 2024-12-28 17:46:50 UTC

arm64: dts: qcom: x1e80100-dell-xps13-9345: Enable HBR3 on external DPs

When no link frequencies are set, msm/dp driver defaults to HBR2 speed.
Explicitly list supported frequencies including HBR3/8.1Gbps for all
external DisplayPort(s).

Signed-off-by: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>

qcom-x1e-6.12 2024-12-19 14:30:35 UTC
UBUNTU: Changelog for Ubuntu-qcom-x1e-6.12.0-21.21

Author: Tobias Heider
Author Date: 2024-12-19 14:23:41 UTC

UBUNTU: Changelog for Ubuntu-qcom-x1e-6.12.0-21.21

x1e-6.12/203-yoga-slim 2024-12-19 13:04:43 UTC
arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add lid switch

Author: Anthony Ruhier
Author Date: 2024-12-18 19:01:45 UTC

arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add lid switch

Add the lid switch for the Lenovo Yoga Slim 7x.

Other x1e80100 laptops use the GPIO pin 92 only, however on the Yoga
Slim 7x this pin seems to be bridged with the pin 71. By default, the
pin 71 is set as output-high, which blocks any event on pin 92.

This patch sets the pin 71 as output-disable and sets the LID switch on
pin 92. This is aligned with how they're configured on Windows:
     GPIO 71 | 0xf147000 | in | func0 | hi | pull up | 16 mA |
ctl=0x000001c3 io=0x00000003
     GPIO 92 | 0xf15c000 | in | func0 | lo | no pull | 2 mA |
ctl=0x00000000 io=0x00000001

Signed-off-by: Anthony Ruhier <aruhier@mailbox.org>
Tested-by: Maya Matuszczyk <maccraft123mc@gmail.com>

x1e-6.12/410-audio 2024-12-10 12:06:44 UTC
UBUNTU: Audio support on X Elite is currently experimental and comes

Author: Tobias Heider
Author Date: 2024-12-10 12:04:28 UTC

UBUNTU: Audio support on X Elite is currently experimental and comes
with a risk of permanently damaging hardware. Add an explicit kernel
command line flag to make sure it doesn't get enabled by accident.

x1e-6.12/420-efi 2024-11-28 12:04:47 UTC
hack: efi/libstub: fix t14s exit_boot_services() failure

Author: Johan Hovold
Author Date: 2024-11-28 08:20:36 UTC

hack: efi/libstub: fix t14s exit_boot_services() failure

The UEFI firmware on the Lenovo ThinkPad T14s is broken and
ExitBootServices() often fails and prevents the kernel from starting:

 EFI stub: Exiting boot services...
 EFI stub: Exit boot services failed.

One bootloader entry may fail to start almost consistently (once in a
while it may start), while a second entry may always work even when the
kernel, dtb and initramfs images are copies of the failing entry on the
same ESP.

This can be worked around by starting and exiting a UEFI shell from the
bootloader or by starting the bootloader manually via the Boot Menu
(F12) before starting the kernel.

Notably starting the kernel automatically from the shell startup.nsh
does not work, while calling the same script manually works.

Experiments have revealed that allocating an event before calling
ExitBootServices() can make the call succeed. There is often no need to
actually signal the event group, but the event must remain allocated
(i.e. CloseEvent() must not be called).

Also with the event signalling, ExitBootServices() sometimes fails when
starting the kernel automatically from a shell startup.nsh, while
systemd-boot seems to always work. This was only observed after removing
some efi_printk() used during the experiments from the stub...

Signed-off-by: Johan Hovold <johan+linaro@kernel.org>

x1e-6.12/204-galaxy-book 2024-11-25 15:15:52 UTC
firmware: qcom: scm: Allow QSEECOM on Samsung Galaxy Book4 Edge

Author: Tobias Heider
Author Date: 2024-10-18 04:07:40 UTC

firmware: qcom: scm: Allow QSEECOM on Samsung Galaxy Book4 Edge

Signed-off-by: Tobias Heider <tobias.heider@canonical.com>

x1e-6.12/202-romulus 2024-11-25 13:25:30 UTC
arm64: dts: qcom: x1e80100-romulus: Set up USB Multiport controller

Author: Konrad Dybcio
Author Date: 2024-09-02 14:50:34 UTC

arm64: dts: qcom: x1e80100-romulus: Set up USB Multiport controller

The USB MP controller is wired up to the USB-A port on the left side
and to the Surface Connector on the right side. Configure it.

While at it, remove a stray double \n.

Signed-off-by: Konrad Dybcio <quic_kdybcio@quicinc.com>
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Link: https://lore.kernel.org/r/20240902-topic-sl7_updates-v1-2-3ee667e6652d@quicinc.com
Signed-off-by: Bjorn Andersson <andersson@kernel.org>

x1e-6.12/400-drm 2024-11-23 16:42:18 UTC
drm/msm/dpu: fix x1e80100 intf_6 underrun/vsync interrupt

Author: Stephan Gerhold
Author Date: 2024-11-13 10:06:08 UTC

drm/msm/dpu: fix x1e80100 intf_6 underrun/vsync interrupt

The IRQ indexes for the intf_6 underrun/vsync interrupts are currently
swapped. DPU_IRQ_IDX(MDP_SSPP_TOP0_INTR, 16) is the actual underrun
interrupt and DPU_IRQ_IDX(MDP_SSPP_TOP0_INTR, 17) is the vsync interrupt.

This causes timeout errors when using the DP2 controllers, e.g.
  [dpu error]enc37 frame done timeout
  *ERROR* irq timeout id=37, intf_mode=INTF_MODE_VIDEO intf=6 wb=-1, pp=2, intr=0
  *ERROR* wait disable failed: id:37 intf:6 ret:-110

Correct them to fix these errors and make DP2 work correctly.

Cc: stable@vger.kernel.org
Fixes: e3b1f369db5a ("drm/msm/dpu: Add X1E80100 support")
Signed-off-by: Stephan Gerhold <stephan.gerhold@linaro.org>

x1e-6.12/100-6.12-next 2024-11-22 16:48:19 UTC
usb: typec: ucsi: glink: be more precise on orientation-aware ports

Author: Dmitry Baryshkov
Author Date: 2024-11-09 00:04:15 UTC

usb: typec: ucsi: glink: be more precise on orientation-aware ports

Instead of checking if any of the USB-C ports have orientation GPIO and
thus is orientation-aware, check for the GPIO for the port being
registered. There are no boards that are affected by this change at this
moment, so the patch is not marked as a fix, but it might affect other
boards in future.

Reviewed-by: Abel Vesa <abel.vesa@linaro.org>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Reviewed-by: Johan Hovold <johan+linaro@kernel.org>
Tested-by: Johan Hovold <johan+linaro@kernel.org>
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Link: https://lore.kernel.org/r/20241109-ucsi-glue-fixes-v2-2-8b21ff4f9fbe@linaro.org
Signed-off-by: Johan Hovold <johan+linaro@kernel.org>

x1e/201-t14s 2024-11-16 17:41:07 UTC
arm64: dts: qcom: x1e78100-t14s: Add display brightness control support

Author: Abel Vesa
Author Date: 2024-11-08 09:20:51 UTC

arm64: dts: qcom: x1e78100-t14s: Add display brightness control support

Signed-off-by: Abel Vesa <abel.vesa@linaro.org>

x1e/202-romulus 2024-11-12 16:13:13 UTC
platform/surface: Add OF support

Author: Konrad Dybcio
Author Date: 2024-08-14 10:27:27 UTC

platform/surface: Add OF support

Add basic support for registering the aggregator module on Device Tree-
based platforms. These include at least three generations of Qualcomm
Snapdragon-based Surface devices:

- SC8180X / SQ1 / SQ2: Pro X,
- SC8280XP / SQ3: Devkit 2023, Pro 9
- X Elite: Laptop 7 / Pro11

Thankfully, the aggregators on these seem to be configured in an
identical way, which allows for using these settings as defaults and
no DT properties need to be introduced (until that changes, anyway).

Based on the work done by Maximilian Luz, largely rewritten.

Signed-off-by: Konrad Dybcio <quic_kdybcio@quicinc.com>
Reviewed-by: Maximilian Luz <luzmaximilian@gmail.com>
Tested-by: Maximilian Luz <luzmaximilian@gmail.com>
Link: https://lore.kernel.org/r/20240814-topic-sam-v3-3-a84588aad233@quicinc.com
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>

142 of 42 results
This repository contains Public information 
Everyone can see this information.