Msm8953 For Arm64 Driver _hot_ -

For the MSM8953 (Snapdragon 625/450) chipset running on ARM64, a highly useful feature enabled through the Linux kernel drivers (specifically in custom ROMs like LineageOS) is the CFQ Group Scheduling support.

Feature Name: CFQ (Completely Fair Queuing) Group Scheduling (CONFIG_CFQ_GROUP_SCHED)

Why it's useful: It optimizes I/O performance by dividing the storage bandwidth among different processes or user groups. On an ARM64-based device, this significantly improves responsiveness when the system is under heavy storage load, preventing apps from freezing while background tasks (like app updates) are running. Other Notable Features Found in MSM8953 Drivers:

WLAN/4G Debugging: Enabling advanced debugging options in the drivers to help diagnose connectivity issues in Android head units. msm8953 for arm64 driver

Clock-Frequency Optimization: Adding missing clock-frequency properties in the device tree (dts) to ensure components operate at their intended, efficient speed. If you can tell me:

Are you compiling a custom kernel or modifying an existing ROM?

What is the main problem you are trying to solve (e.g., lag, battery life, a specific component not working)? LineageOS/android_kernel_motorola_msm8953 - GitHub For the MSM8953 (Snapdragon 625/450) chipset running on

Here’s a technical review of MSM8953 (also known as Snapdragon 625/626) support for arm64 drivers, focusing on the mainline Linux kernel and Android common kernel perspectives.

msm8953 (ARM64) — full driver overview

The Silicon

The MSM8953 is inherently a 64-bit processor, featuring eight ARM Cortex-A53 cores (quad-core cluster @ 2.0GHz or 2.2GHz). It uses the ARMv8-A architecture, meaning it fully supports the ARM64 instruction set. However, here lies the first critical nuance: The modem firmware, audio DSP (Hexagon 546), and certain hardware accelerators were delivered by Qualcomm as 32-bit (ARMv7) binaries.

Why? In 2016, Android was still transitioning from 32-bit to 64-bit. To maintain compatibility and reduce memory footprint, OEMs shipped MSM8953 devices with 32-bit userspace (android32) but a 64-bit kernel. This hybrid approach haunts modern developers. Move 32-bit

Step 3: Extract and Convert Proprietary Blobs

From your device’s stock ROM (Android 9 typically), extract /vendor partition. Then separate:

• Move 32-bit .so files to /vendor/lib
• Move 64-bit .so files to /vendor/lib64

For the camera HAL, you may need to use libhwbinder’s 32-bit service:

service cameraserver /system/bin/cameraserver
    class main
    user cameraserver
    # Force 32-bit execution
    environment LD_LIBRARY_PATH /vendor/lib:/system/lib

10. Resources and source-tree pointers (where to look)

• Kernel: arch/arm64/boot/dts/qcom (msm8953 dts files)
• drivers/gpu/kgsl
• drivers/net/wireless (ath10k, brcmfmac)
• drivers/media/platform/msm (camera)
• drivers/soc/qcom, drivers/clk/qcom, drivers/reset/qcom
• drivers/usb/dwc3 and drivers/usb/phy/qcom
• sound/soc/qcom
• Android device trees and vendor trees for msm8953-based devices (GitHub/git repositories for specific OEMs) (Note: I did not include direct web links.)