Acer Swift SFG14-01 Camera Support not working on Linux

Acer Swift SFG14-01 Camera Support not working on Linux

[AHMAD YASEEN]

Hello Acer Support and Qualcomm/Linux Camera Maintainers,

We are working to enable the built-in RGB camera on an Acer Swift
SFG14-01, board Bluetang_SX1, with Qualcomm Snapdragon X Plus
(qcom,x1p42100). We need assistance identifying the correct hardware
configuration and Linux enablement path.

Current environment and findings:

Ubuntu 26.04, kernel 7.0.0-30-generic; device-tree boot.

No USB camera detected; the internal camera uses the MIPI camera path.

CCI1 at ac16000 and CAMSS at acb7000 are disabled in the live device
tree, with no corresponding platform devices.

CCI0 registers adapters, but an experimental HM1092 probe returned
timeout -110. This was based on an unverified sensor configuration and
does not establish an RGB sensor or hardware failure.

No RGB chip-ID has been obtained. No media/video devices are present,
and libcamera lists no cameras.

A controller-only CCI1 boot test has been prepared but has not yet
been validated on hardware.

The Windows driver files available locally contain multiple sensor
profiles, including imx688 and ov08x. We have not established which
profile applies to this exact unit. Existing experimental GPIO,
address and power settings are also unverified.

Could Acer’s platform engineering team confirm:

The exact RGB sensor and camera module fitted to this model/SKU.

The CCI controller/master and 7-bit I2C address.

Supply rails and voltages, power sequencing, reset/enable signals and
MCLK requirements.

CSI interface and lane configuration.

Any available Linux device-tree configuration, driver patches or
supported image.

For the Qualcomm/Linux maintainers, we would appreciate guidance on
the minimum CCI1 configuration and dependencies for this platform, any
existing SFG14-01 camera enablement work, and the diagnostic evidence
needed to investigate further.

We can provide the kernel boot logs, kernel configuration, baseline
and live device trees, minimal CCI1 patch, and Windows hardware IDs
and driver-profile details. Serial number/SNID information can be
provided privately to Acer.

Our immediate objective is to bring up the correct CCI controller and
obtain a repeatable RGB sensor chip-ID before proceeding to capture
and libcamera integration.

Please route this request to the appropriate platform or camera
engineer if necessary.
Ahmad

Re: Acer Swift SFG14-01 Camera Support not working on Linux

[Bryan O'Donoghue]

On 09/09/2026 08:41, AHMAD YASEEN wrote:
> We can provide the kernel boot logs, kernel configuration, baseline
> and live device trees, minimal CCI1 patch, and Windows hardware IDs
> and driver-profile details. Serial number/SNID information can be
> provided privately to Acer.
> 
> Our immediate objective is to bring up the correct CCI controller and
> obtain a repeatable RGB sensor chip-ID before proceeding to capture
> and libcamera integration.

The RGB sensor and _should_ be on the same CCI and CSIPHY as the other 
x1e platforms.

Windows actually discloses alot of the information you need.

cd /mnt/windows; find . -name "*sensor*.bin" -print

For me on the Dell Inspiron that show ov02e10.bin and hm1092.bin for the 
RGB and Greyscale sensors respectively.

So you don't necessarily need Acer to provide information though, it'd 
be nice.

You should add a dump of your DSDT here:

https://github.com/aarch64-laptops/build/tree/master/misc

Same one ?

https://github.com/aarch64-laptops/build/tree/master/misc/acer-sfa14-11

...

You have a USB camera no ?

DSDT Device(WCAM)

https://github.com/aarch64-laptops/build/blob/57a8b779e1ad1f08fb5c05b74c6d2d5975706a92/misc/acer-sfa14-11/dsdt.dsl#L50015

Device (WCAM)
                     {
                         Name (_ADR, One)  // _ADR: Address
                         Name (_PLD, Package (0x01)  // _PLD: Physical 
Location of Device
                         {
                             ToPLD (
                                 PLD_Revision           = 0x2,
                                 PLD_IgnoreColor        = 0x1,
                                 PLD_Red                = 0x0,
                                 PLD_Green              = 0x0,
                                 PLD_Blue               = 0x0,
                                 PLD_Width              = 0x0,
                                 PLD_Height             = 0x0,
                                 PLD_UserVisible        = 0x1,
                                 PLD_Dock               = 0x0,
                                 PLD_Lid                = 0x1,
                                 PLD_Panel              = "FRONT",
                                 PLD_VerticalPosition   = "UPPER",
                                 PLD_HorizontalPosition = "CENTER",
                                 PLD_Shape              = "UNKNOWN",
                                 PLD_GroupOrientation   = 0x0,
                                 PLD_GroupToken         = 0x0,
                                 PLD_GroupPosition      = 0x0,
                                 PLD_Bay                = 0x0,
                                 PLD_Ejectable          = 0x0,
                                 PLD_EjectRequired      = 0x0,
                                 PLD_CabinetNumber      = 0x0,
                                 PLD_CardCageNumber     = 0x0,
                                 PLD_Reference          = 0x0,
                                 PLD_Rotation           = 0x0,
                                 PLD_Order              = 0x0,
                                 PLD_VerticalOffset     = 0xFFFF,
                                 PLD_HorizontalOffset   = 0xFFFF)

                         })
                     }

Switch on host controller for usb_2 and the USB should should power it. 
At a guess its probably a UVC video device.

---
bod