[Bug 221780] New: Samsung Galaxy Book Pro 6 (Core Ultra X7 358H): camera unavailable because samsung_galaxybook fails CSFI "block recording" query

[Bug 221780] New: Samsung Galaxy Book Pro 6 (Core Ultra X7 358H): camera unavailable because samsung_galaxybook fails CSFI "block recording" query

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=221780

            Bug ID: 221780
           Summary: Samsung Galaxy Book Pro 6 (Core Ultra X7 358H): camera
                    unavailable because samsung_galaxybook fails CSFI
                    "block recording" query
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Platform_x86
          Assignee: drivers_platform_x86@kernel-bugs.osdl.org
          Reporter: tm@tmgldn.com
        Regression: No

Created attachment 310494
  --> https://bugzilla.kernel.org/attachment.cgi?id=310494&action=edit
uname.txt, lspci.txt, dmesg.txt, journal.txt, ovti08f4-status.txt, dsdt.dsl

drivers/platform/x86/samsung-galaxybook.c

The integrated camera is not detected under Linux on a Samsung Galaxy Book Pro
6 with an Intel Core Ultra X7 358H (Panther Lake).

The Intel IPU7 driver loads successfully, but no camera sensor is discovered
because the Samsung platform driver fails to query the firmware's block
recording feature.

The driver logs:

`acpi SAM0430:00: failed to execute CSFI; device responded with failure code
0xff`

After this, the camera sensor remains disabled and libcamera cannot discover
it.

## System

* Laptop: Samsung Galaxy Book Pro 6
* CPU: Intel Core Ultra X7 358H
* Kernel: (see attached uname.txt)
* Distribution: Arch Linux
* IPU PCI ID: 8086:b05d
* Camera sensor ACPI ID: OVTI08F4

## Observed behaviour

The IPU7 driver loads successfully.

`v4l2-ctl --list-devices` shows the IPU.

`libcamera` reports:

`No sensor found for /dev/media0`

Kernel log contains:

```
intel-ipu7 ... no subdev found in graph
acpi SAM0430:00: failed to execute CSFI; device responded with failure code
0xff
```

The camera sensor exists in ACPI:

`OVTI08F4`

but

`/sys/bus/acpi/devices/OVTI08F4:00/status`

contains:

`0`

The `samsung_galaxybook` driver loads correctly.

Working features include:

* keyboard backlight
* platform profile

The firmware attributes directory exists but contains no camera-related
attributes.

The privacy key generates a normal F11 key event and no ACPI notification is
produced.

## Investigation

I inspected the current `drivers/platform/x86/samsung-galaxybook.c` source.

The failure occurs during the `CSFI` request used for
`GB_SASB_BLOCK_RECORDING`.

The ACPI method itself exists in the firmware:

```asl
Method (CSFI, 1, Serialized)
{
    Return (SAWS (Arg0))
}
```

The AML simply forwards the request to `SAWS`.

`SAWS` returns the firmware response.

The Linux driver reaches the `GB_GUNM_FAIL` check and reports:

`failed to execute CSFI; device responded with failure code 0xff`

This suggests the firmware rejects the request rather than the ACPI method
itself failing.

Because this query fails, the camera privacy feature is never initialised and
the sensor remains unavailable.

## Expected behaviour

The Samsung platform driver should successfully initialise the camera/privacy
feature on this model so that the camera sensor becomes available to the Intel
IPU stack.

## Attachments

* uname.txt
* lspci.txt
* dmesg.txt
* journal.txt
* ovti08f4-status.txt
* dsdt.dsl

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.