Skip to content

Prepare qcom-next based on tag 'Linux 7.2-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git#806

Open
Salendarsingh Gaud (sgaud-quic) wants to merge 1135 commits into
qualcomm-linux:qcom-next-stagingfrom
sgaud-quic:qcom-next-staging-7.2-rc1-20260704
Open

Prepare qcom-next based on tag 'Linux 7.2-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git#806
Salendarsingh Gaud (sgaud-quic) wants to merge 1135 commits into
qualcomm-linux:qcom-next-stagingfrom
sgaud-quic:qcom-next-staging-7.2-rc1-20260704

Conversation

@sgaud-quic

Copy link
Copy Markdown
Contributor

Name SHA Commits

tech/bsp/clk dcf6518 22
tech/bsp/devfreq 5a26797 7
tech/bsp/soc-infra 600ea9c 24
tech/bsp/pinctrl 79149ef 1
tech/bsp/remoteproc ce284ee 9
tech/bus/peripherals fedd8c6 6
tech/bus/pci/all ebd808f 4
tech/bus/pci/phy ec405c8 4
tech/bus/usb/dwc 9dd47ad 3
tech/bus/usb/phy c3aa7d5 35
tech/debug/hwtracing ee4a490 31
tech/pmic/misc 6fb618c 8
tech/mem/iommu 44df12a 8
tech/mm/audio/all 88b8f29 8
tech/mm/camss c394dfb 32
tech/mm/drm b480a07 65
tech/mm/fastrpc e014e35 11
tech/mm/video dc89f72 32
tech/mm/gpu 0b8d9f4 7
tech/net/ath a915440 14
tech/pm/power bb88701 13
tech/pm/thermal d36b3ee 7
tech/security/crypto c36112e 14
tech/security/ice beabac0 9
tech/storage/all d86d915 4
tech/all/dt/qcs6490 d705803 21
tech/all/dt/qcs9100 3853a49 91
tech/all/dt/qcs8300 e93aa15 24
tech/all/dt/qcs615 1cc303d 8
tech/all/dt/agatti c828f10 1
tech/all/dt/hamoa 723e3ef 32
tech/all/dt/glymur 2d9c5be 28
tech/all/dt/kaanapali 40ea4b6 17
tech/all/dt/pakala b2e5e96 12
tech/all/config 2f8abb9 69
tech/overlay/dt cb96f06 68
tech/all/workaround 2a67b15 26
tech/mproc/all 0aa90b7 3
tech/noup/debug/all cbdd4bb 26
tech/hwe/unoq a2d85fe 4
early/hwe/shikra/drivers f5654fe 160
early/hwe/shikra/dt e6da759 122

swatagar and others added 30 commits July 3, 2026 13:51
Add support for the GL3590 4 ports USB3.2 hub. This allows to control its
reset pins with a gpio.

Signed-off-by: Swati Agarwal <swati.agarwal@oss.qualcomm.com>
Add the binding for the USB3.2 Genesys Logic GL3590 hub.

Signed-off-by: Swati Agarwal <swati.agarwal@oss.qualcomm.com>
…h hardware

The Qualcomm Embedded USB Debugger (EUD) can intercept one or two
independent High-Speed UTMI paths, depending on the SoC. Each path is
distinct with its own HS-PHY interface, connector/controller wiring, and
UTMI routing behavior. The EUD hardware sits between the USB2 PHY and
the USB controller on each path.

The existing binding models only a single UTMI path and does not provide
a way to associate the required High-Speed USB PHY. EUD relies on the
HS-PHY on the selected UTMI path for link signalling and correct operation
of the hardware.

Historically, EUD has worked on platforms that use a single UTMI path
because the USB controller maintains ownership of the PHY during
enumeration and normal operation. This implicit relationship allowed
EUD to function even though the dependency on the PHY was not described
in the binding. However, this behavior is not guaranteed by hardware.
The current binding description is not sufficient for SoCs that expose
two independent UTMI paths, where the PHY association and port wiring
must be explicitly described.

Introduce per-path eud-path child nodes so each UTMI path can describe
its HS-PHY, port connections, and the role‑switching capability of its
associated USB port.

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
Link: https://lore.kernel.org/linux-usb/20260126233830.2193816-2-elson.serrao@oss.qualcomm.com/
EUD can be mapped to either the primary USB port or the secondary USB port
depending on the value of the EUD_PORT_SEL register. Add a 'port' sysfs
attribute to allow userspace to select which port EUD should operate on
and update the ABI documentation. This is needed for systems with dual
USB ports where EUD needs to be accessible on either port depending on the
system configuration and use case.

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Link: https://lore.kernel.org/linux-usb/20260126233830.2193816-3-elson.serrao@oss.qualcomm.com/
EUD hardware can support multiple High-Speed USB paths, each routed
through its own PHY. The active path is selected in hardware via the
EUD_PORT_SEL register. As a High-Speed hub, EUD requires access to the
High-Speed PHY associated with the active UTMI path. To support this
multi-path capability, the driver must manage PHY resources on a per-path
basis, ensuring that the PHY for the currently selected path is properly
initialized and powered.

This patch restructures the driver to implement per-path PHY management.
The driver now powers the appropriate PHY based on the selected and
enabled UTMI path, ensuring correct operation when EUD is enabled.

Supporting this requires describing the available UTMI paths and their
corresponding PHYs in Device Tree. This updates DT requirements and is
not backward compatible with older DTs that lacked this description.
Historically, EUD appeared to work on single-path systems because the
USB controller kept the PHY initialized. However, EUD is designed to
operate independently of the USB controller and therefore requires
explicit PHY control.

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
Link: https://lore.kernel.org/linux-usb/20260126233830.2193816-4-elson.serrao@oss.qualcomm.com/
The EUD hardware can support multiple High-Speed USB paths, each connected
to different USB controllers. The current implementation uses a single
chip-level role switch, which cannot properly handle multi-path
configurations where each path needs independent role management. Since
EUD is physically present between the USB connector and the controller,
it should also relay the role change requests from the connector.

Restructure the driver to support per-path role switches and remove the
chip-level role switch. Additionally, as EUD need not modify the USB
role upon enabling, remove the unnecessary role switch call from
enable_eud().

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
Link: https://lore.kernel.org/linux-usb/20260126233830.2193816-5-elson.serrao@oss.qualcomm.com/
Currently enable_store() allows operations irrespective of the EUD state,
which can result in redundant operations. Avoid this by adding duplicate
state checks to skip requests when EUD is already in the desired state.
Additionally, improve error handling with explicit logging to provide
better feedback.

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Link: https://lore.kernel.org/linux-usb/20260126233830.2193816-6-elson.serrao@oss.qualcomm.com/
EUD functions by presenting itself as a USB device to the host PC for
debugging, making it incompatible in USB host mode configurations.
Enabling EUD, when in host mode can also cause the USB controller to
misbehave as the EUD hub can only have one upstream facing port.

Handle below two scenarios to prevent these conflicts:
1. Prevent user from enabling EUD via sysfs when the USB port is
   in host mode.
2. Automatically disable EUD when USB port switches to host mode
   and re-enable it when exiting host mode.

This ensures consistent state management without creating conflicts
between the EUD debug hub and the USB controller.

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
Link: https://lore.kernel.org/linux-usb/20260126233830.2193816-7-elson.serrao@oss.qualcomm.com/
EUD provides virtual USB attach/detach events to simulate cable
plug/unplug while maintaining the physical debug connection. However,
the current implementation incorrectly sets the USB role to HOST on
virtual detach, which doesn't represent the disconnected state.

Fix the virtual detach handling by setting the USB role to NONE
instead of HOST, correctly representing the disconnected state.

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
https://lore.kernel.org/linux-usb/20260126233830.2193816-8-elson.serrao@oss.qualcomm.com/
The EUD node does not match the current binding and maps USB endpoints
to the secondary controller. This SoC supports EUD only on the primary
High-Speed USB path. The binding also requires a per-path PHY reference.

Model the primary UTMI path as a child node with the required PHY and an
empty ports graph. Leave endpoint mapping to board DTS files, and remove
the secondary mapping and associated ports so the description conforms
to the binding.

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
iLink: https://lore.kernel.org/linux-usb/20260126233830.2193816-9-elson.serrao@oss.qualcomm.com/
…nality

On this board, EUD resides on the primary High-Speed USB data path between
the connector and the DWC3 controller. Update the device tree connections
to correctly map the connector and controller endpoints, and describe
role-switch capability on the EUD primary path.

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
Link: https://lore.kernel.org/linux-usb/20260126233830.2193816-10-elson.serrao@oss.qualcomm.com/
For systems where the ID pin isn't available as gpio use the ATTACHED_STATE
register instead to control vbus.

>From the datasheet:
"This is an additional method to communicate attach other
than the ID pin. These bits can be read by the application to
determine what was attached."

Use this method if id-gpios property is not set, but the connector node
has vbus-supply defined.

Check regulator state as peripheral and detach can disable vbus.

Signed-off-by: Jan Remmet <j.remmet@phytec.de>
The HD3SS3220's interrupt is disabled during system suspend, so a USB‑C
cable connect/attach event cannot wake the system. This prevents resume
from low‑power modes when the port controller is expected to act as a
wakeup source.

Add wakeup support by:

- Initialize the device as wakeup‑capable.
- Enable the HD3SS3220 IRQ as a wakeup interrupt.
- Add suspend/resume callbacks to enable or disable the IRQ for wakeup
depending on the device's wakeup configuration.

With this, USB‑C cable insertion correctly wakes the system from suspend.

Link: https://lore.kernel.org/all/20260215183325.3836178-2-swati.agarwal@oss.qualcomm.com/
Signed-off-by: Swati Agarwal <swati.agarwal@oss.qualcomm.com>
… functionality"

This reverts commit e65028c.

Issue is observed with this commit e65028c leading to crash,
with following call stack

[   19.706310][   T73] Call trace:
[   19.706312][   T73]  usb_role_switch_unregister+0x28/0x70 (P)
[   19.706319][   T73]  eud_role_switch_release+0x30/0x78 [qcom_eud]
[   19.884972][   T73]  devm_action_release+0x1c/0x30
[   19.884981][   T73]  release_nodes+0x70/0x120
[   19.884987][   T73]  devres_release_all+0x98/0xf0
[   19.884995][   T73]  device_unbind_cleanup+0x20/0x98
[   19.885000][   T73]  really_probe+0x184/0x3f0
[   19.885005][   T73]  __driver_probe_device+0x88/0x190
[   19.885010][   T73]  driver_probe_device+0x44/0x120
[   19.885015][   T73]  __device_attach_driver+0xc4/0x178
[   19.885020][   T73]  bus_for_each_drv+0x90/0xf8
[   19.885027][   T73]  __device_attach+0xa8/0x1d8
[   19.885032][   T73]  device_initial_probe+0x58/0x68
[   19.885037][   T73]  bus_probe_device+0x40/0xb8
[   19.885041][   T73]  deferred_probe_work_func+0xbc/0x128
[   19.885046][   T73]  process_one_work+0x180/0x450
[   19.885055][   T73]  worker_thread+0x26c/0x388
[   19.885062][   T73]  kthread+0x120/0x140
[   19.885068][   T73]  ret_from_fork+0x10/0x20
[   19.885079][   T73] Code: f9000bf3 aa0003f3 b140041f 54000168 (390c901f)
[   19.885083][   T73] ---[ end trace 0000000000000000 ]---
[   19.885088][   T73] Kernel panic - not syncing: Oops: Fatal exception
[   19.885091][   T73] SMP: stopping secondary CPUs

Revert commit for now.

Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
This reverts commit 09ed0b6.

Issue is observed with this commit 09ed0b6 leading to crash,
with following call stack

[   19.706310][   T73] Call trace:
[   19.706312][   T73]  usb_role_switch_unregister+0x28/0x70 (P)
[   19.706319][   T73]  eud_role_switch_release+0x30/0x78 [qcom_eud]
[   19.884972][   T73]  devm_action_release+0x1c/0x30
[   19.884981][   T73]  release_nodes+0x70/0x120
[   19.884987][   T73]  devres_release_all+0x98/0xf0
[   19.884995][   T73]  device_unbind_cleanup+0x20/0x98
[   19.885000][   T73]  really_probe+0x184/0x3f0
[   19.885005][   T73]  __driver_probe_device+0x88/0x190
[   19.885010][   T73]  driver_probe_device+0x44/0x120
[   19.885015][   T73]  __device_attach_driver+0xc4/0x178
[   19.885020][   T73]  bus_for_each_drv+0x90/0xf8
[   19.885027][   T73]  __device_attach+0xa8/0x1d8
[   19.885032][   T73]  device_initial_probe+0x58/0x68
[   19.885037][   T73]  bus_probe_device+0x40/0xb8
[   19.885041][   T73]  deferred_probe_work_func+0xbc/0x128
[   19.885046][   T73]  process_one_work+0x180/0x450
[   19.885055][   T73]  worker_thread+0x26c/0x388
[   19.885062][   T73]  kthread+0x120/0x140
[   19.885068][   T73]  ret_from_fork+0x10/0x20
[   19.885079][   T73] Code: f9000bf3 aa0003f3 b140041f 54000168 (390c901f)
[   19.885083][   T73] ---[ end trace 0000000000000000 ]---
[   19.885088][   T73] Kernel panic - not syncing: Oops: Fatal exception
[   19.885091][   T73] SMP: stopping secondary CPUs

Revert commit for now.

Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
…t handling"

This reverts commit 7104631.

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
This reverts commit 583d6fc.

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
This reverts commit eb5da51.

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
This reverts commit e7e656c.

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
…ntrol"

This reverts commit e2541a8.

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
…election"

This reverts commit c042ed7.

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
…ulti-path hardware"

This reverts commit cfe135b.

Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
Add an optional consumer→provider phandle on USB connectors to reference
the USB role-switch provider when no direct graph link exists. The DRD
controller remains the provider via its 'usb-role-switch' property.

Link: https://lore.kernel.org/all/20260223191042.825136-2-elson.serrao@oss.qualcomm.com/
Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
…iguration

EUD hardware supports debugging on up to two USB ports depending on the
SoC configuration. Debugging can be selected on either the primary or
secondary USB port as controlled by the EUD_PORT_SELECT register.

Extend the binding to support dual-port configurations by adding port@2
and port@3 for secondary USB controller and Type-C connector connections.

Link: https://lore.kernel.org/all/20260309203337.803986-2-elson.serrao@oss.qualcomm.com/
Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
EUD can be mapped to either the primary USB port or the secondary USB port
depending on the value of the EUD_PORT_SEL register. Add a 'port' sysfs
attribute to allow userspace to select which port EUD should operate on
and update the ABI documentation. This is needed for systems with dual
USB ports where EUD needs to be accessible on either port depending on the
system configuration and use case.

Link: https://lore.kernel.org/all/20260309203337.803986-3-elson.serrao@oss.qualcomm.com/
Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
EUD hardware can support multiple High-Speed USB ports, each routed
through its own PHY. The active port is selected in hardware via the
EUD_PORT_SEL register. As a High-Speed hub, EUD requires access to
the High-Speed PHY associated with the active port. To support this
multi-port capability, the driver must manage PHY resources on a
per-port basis, ensuring that the PHY for the currently selected
port is properly initialized and powered.

This patch adds per-port PHY management to the driver. The driver
now powers the appropriate PHY based on the selected and enabled
port, ensuring correct operation when EUD is enabled.

Historically, EUD appeared to work on single-port systems because
the USB controller kept the PHY initialized. However, EUD is
designed to operate independently of the USB controller and
therefore requires explicit PHY control for proper operation.

Link: https://lore.kernel.org/all/20260309203337.803986-4-elson.serrao@oss.qualcomm.com/
Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
The EUD hardware can support multiple High-Speed USB ports, each
connected to different USB controllers. The current implementation
uses a single chip-level role switch, which cannot properly handle
multi-port configurations where each USB port can operate in
different role.

Restructure the driver to support per-port role switches.
Additionally, remove the unnecessary role switch call from
enable_eud() as EUD need not modify the USB role upon enabling.

Link: https://lore.kernel.org/all/20260309203337.803986-5-elson.serrao@oss.qualcomm.com/
Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
Currently enable_store() allows operations irrespective of the EUD state,
which can result in redundant operations. Avoid this by adding duplicate
state checks to skip requests when EUD is already in the desired state.
Additionally, improve error handling with explicit logging to provide
better feedback.

Link: https://lore.kernel.org/all/20260309203337.803986-6-elson.serrao@oss.qualcomm.com/
Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
EUD provides virtual USB attach/detach events to simulate cable
plug/unplug while maintaining the physical debug connection. However,
the current implementation incorrectly sets the USB role to HOST on
virtual detach, which doesn't represent the disconnected state.

Fix the virtual detach handling by setting the USB role to NONE
instead of HOST, correctly representing the disconnected state.

Link: https://lore.kernel.org/all/20260309203337.803986-7-elson.serrao@oss.qualcomm.com/
Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
EUD functions by presenting itself as a USB device to the host PC for
debugging, making it incompatible with USB host mode configurations.

Handle below two scenarios to prevent these conflicts:
1. Prevent user from enabling EUD via sysfs when the USB port is
   in host mode.
2. Automatically disable EUD when USB port switches to host mode
   and re-enable it when exiting host mode. This is achieved via
   the exported qcom_eud_usb_role_notify() API that allows the USB
   controller driver to notify EUD of role changes.

This ensures consistent state management without creating conflicts
between the EUD debug hub and the USB controller.

Link: https://lore.kernel.org/all/20260309203337.803986-8-elson.serrao@oss.qualcomm.com/
Signed-off-by: Elson Serrao <elson.serrao@oss.qualcomm.com>
# Conflicts:
#	drivers/remoteproc/qcom_q6v5_pas.c
# Conflicts:
#	arch/arm64/boot/dts/qcom/monaco.dtsi
# Conflicts:
#	arch/arm64/boot/dts/qcom/Makefile
# Conflicts:
#	arch/arm64/boot/dts/qcom/qcs8300-ride.dts
#	drivers/bluetooth/hci_qca.c
#	drivers/phy/qualcomm/phy-qcom-qmp-pcie.c
# Conflicts:
#	drivers/soc/qcom/smem.c
# Conflicts:
#	drivers/dma/qcom/bam_dma.c
#	drivers/gpu/drm/bridge/lontium-lt9611c.c
#	drivers/misc/fastrpc.c
#	sound/soc/qcom/qdsp6/q6prm.h
# Conflicts:
#	Documentation/devicetree/bindings/sound/qcom,q6apm-dai.yaml
Adding merge log file and topic_SHA1 file

Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@sgaud-quic Salendarsingh Gaud (sgaud-quic) force-pushed the qcom-next-staging-7.2-rc1-20260704 branch from b943d19 to 50dbb1c Compare July 4, 2026 06:41
@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #806

PR: #806
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/28708395886

# Error File:Line PR-introduced? Root Cause
1 'dest_domain' undeclared sound/soc/qcom/qdsp6/audioreach.c:1108 Yes New function audioreach_audio_if_set_media_format() uses dest_domain variable without declaring it. All other functions in the PR correctly declare u16 dest_domain = audioreach_gpr_dest_domain(graph->apm->gdev); before using it.

Verdict

1 of 1 errors is introduced by this PR.

📎 Detailed analysis: Full report

@qlijarvis

Copy link
Copy Markdown

🔨 Build Failure Analysis — PR #806

PR: #806
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/28708395886

# Error File:Line PR-introduced? Root Cause
1 'dest_domain' undeclared sound/soc/qcom/qdsp6/audioreach.c:1108 Yes New function audioreach_audio_if_set_media_format() uses dest_domain variable without declaring it

Verdict

The single compilation error is introduced by this PR. The new function added by the PR is missing a variable declaration that all other similar functions in the same file correctly include.

📎 Detailed analysis: Full report

DRM bridge atomic callbacks now pass struct drm_atomic_commit, and
the atomic helper functions also expect that type. The lt9611c
driver still declares its callbacks with struct drm_atomic_state,
which makes the callback assignments and helper calls fail to build
with incompatible pointer type errors.

Update the lt9611c callback signatures to match the current DRM
bridge API.

Fixes: 96d1cfe ("drm/bridge: Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI driver")
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@sgaud-quic Salendarsingh Gaud (sgaud-quic) force-pushed the qcom-next-staging-7.2-rc1-20260704 branch from 01ce744 to 644312f Compare July 4, 2026 14:56
@qcomlnxci

Copy link
Copy Markdown

Test Matrix

Test Case glymur-crd hamoa-iot-evk kaanapali-mtp lemans-evk monaco-evk qcs615-ride qcs6490-rb3gen2 qcs8300-ride qcs9100-ride-r3 sm8750-mtp
BT_FW_KMD_Service ✅ Pass ❌ Fail ❌ Fail ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
BT_ON_OFF ✅ Pass ⚠️ skip ⚠️ skip ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
BT_SCAN ✅ Pass ◻️ ⚠️ skip ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
CPUFreq_Validation ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
CPU_affinity ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
DSP_AudioPD ⚠️ skip ◻️ ◻️ ◻️ ◻️ ⚠️ skip ✅ Pass ✅ Pass ⚠️ skip ✅ Pass
Ethernet ⚠️ skip ⚠️ skip ⚠️ skip ◻️ ◻️ ⚠️ skip ⚠️ skip ⚠️ skip ⚠️ skip ⚠️ skip
Freq_Scaling ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
GIC ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
IPA ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
Interrupts ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
OpenCV ✅ Pass ◻️ ◻️ ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
PCIe ✅ Pass ✅ Pass ❌ Fail ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ❌ Fail
Probe_Failure_Check ✅ Pass ❌ Fail ✅ Pass ◻️ ◻️ ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail
RMNET ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
UFS_Validation ⚠️ skip ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
USBHost ✅ Pass ❌ Fail ❌ Fail ◻️ ◻️ ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail
WiFi_Firmware_Driver ✅ Pass ◻️ ❌ Fail ◻️ ◻️ ❌ Fail ❌ Fail ❌ Fail ❌ Fail ❌ Fail
WiFi_OnOff ✅ Pass ◻️ ⚠️ skip ◻️ ◻️ ✅ Pass ✅ Pass ⚠️ skip ⚠️ skip ⚠️ skip
adsp_remoteproc ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ❌ Fail ✅ Pass
cdsp_remoteproc ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ❌ Fail ✅ Pass
gpdsp_remoteproc ⚠️ skip ⚠️ skip ⚠️ skip ◻️ ◻️ ⚠️ skip ⚠️ skip ✅ Pass ❌ Fail ⚠️ skip
hotplug ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
irq ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
kaslr ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
pinctrl ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
qcom_hwrng ✅ Pass ◻️ ◻️ ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
remoteproc ❌ Fail ✅ Pass ❌ Fail ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ❌ Fail ✅ Pass
rngtest ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
shmbridge ✅ Pass ✅ Pass ✅ Pass ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
smmu ✅ Pass ❌ Fail ✅ Pass ◻️ ◻️ ❌ Fail ✅ Pass ✅ Pass ❌ Fail ✅ Pass
watchdog ✅ Pass ◻️ ◻️ ◻️ ◻️ ✅ Pass ✅ Pass ✅ Pass ✅ Pass ✅ Pass
wpss_remoteproc ⚠️ skip ⚠️ skip ⚠️ skip ◻️ ◻️ ✅ Pass ✅ Pass ⚠️ skip ⚠️ skip ⚠️ skip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.