Repository navigation
libcamera 0.7.2-4.23, kernel config: the Pixel 9a's main camera autofocus - #494
Conversation
|
Thanks for this, and for being so clear in the description about what you Two changes to the record, please:
One small addition I'd like in the notes as well: since stock puts the This merges after linux-omarchy-mobile#213, since the config line names |
…ocus The 9a's main camera focuses through an onsemi LC898129, which now has a lens driver (linux-omarchy-mobile#213). Build it as a module next to the 7 Pro's SEM1215SA (CONFIG_VIDEO_LC898129=m), and turn on contrast autofocus in the S5KGN8 tuning file (libcamera 0057), with the coarse and fine steps of the 7 Pro's main camera. device/tegu/NOTES.md records where the register map came from, which registers were written while working it out (only the focus target), and what was measured on the phone: the controller's registers, the 12-bit focus target and its Hall read-back, which end is near, and omacam focusing on a subject at about 25 cm, on libcamera 4.22 with the Af lines added by hand. DEVICES.md adds the autofocus to the 9a's camera cell, in review with the kernel PR, and says the far end isn't checked yet. The board's lens node is in the notes; it waits for the 9a's camera device tree (linux-omarchy-mobile#164) and isn't in a pull request yet, as the camera cell says. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
b70c56f to
dbc650a
Compare
|
Thanks, and for checking the sums and the tuning file. Force-pushed (one commit, amended):
|
|
Thanks, all three are done, and the list of every register you read and The re-push only touches the notes and DEVICES.md, so my earlier checks of Since yesterday another PR rewrote the Pixel 8 Pro row, the line just below |
# Conflicts: # device/tegu/NOTES.md # docs/DEVICES.md
…ocus (derekross#494) The 9a's main camera focuses through an onsemi LC898129, which now has a lens driver (linux-omarchy-mobile#213). Build it as a module next to the 7 Pro's SEM1215SA (CONFIG_VIDEO_LC898129=m), and turn on contrast autofocus in the S5KGN8 tuning file (libcamera 0057), with the coarse and fine steps of the 7 Pro's main camera. device/tegu/NOTES.md records where the register map came from, which registers were written while working it out (only the focus target), and what was measured on the phone: the controller's registers, the 12-bit focus target and its Hall read-back, which end is near, and omacam focusing on a subject at about 25 cm, on libcamera 4.22 with the Af lines added by hand. DEVICES.md adds the autofocus to the 9a's camera cell, in review with the kernel PR, and says the far end isn't checked yet. The board's lens node is in the notes; it waits for the 9a's camera device tree (linux-omarchy-mobile#164) and isn't in a pull request yet, as the camera cell says. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
What and why
The Pixel 9a's main camera gets contrast autofocus, as the Pixel 7 Pro has (announced in #28). Its focus runs through an onsemi LC898129, and the lens driver for it is linux-omarchy-mobile#213. This PR is the repo side:
kernel/configs/omamobile.config:CONFIG_VIDEO_LC898129=m, next to the SEM1215SA.Afin the S5KGN8 tuning file (coarse 8, fine 32, as on the 7 Pro's main camera), and the old "no autofocus until the lens has a driver" comment removed. README row added.device/tegu/NOTES.md: what I measured on the phone. That covers the controller and its focus registers, the 12-bit target and its Hall read-back, which end is near, and the lens node the board needs.docs/DEVICES.md: the autofocus in the 9a's Cameras cell, "in review" with the kernel PR, and noting that the far end is not checked yet.The board's lens node (4 lines in
zumapro-tegu.dts) isn't in either PR. It depends on the camera device tree in linux-omarchy-mobile#164 and is written out in the notes and in #213.Device and build
uname -r):7.3.0-rc6-omamobile-push1-gd00d9fd2272f. It's a local build:omamobile+ kernel device/tegu USB-HOST-PLAN: H2b, H4 and H5 ran on 2026-10-30 #178, Some websites stop loading on Wi-Fi after unplugging the USB cable #103, device/tegu FINGERPRINT-PLAN: the LDO15S rule names SLEEP-PLAN S2's one exception #164's camera DT, docs: add a roadmap for the Pixel 8 Pro (husky) #213 and the lens node.Checks (no phone needed)
tools/pr-check origin/mainpassestests/allpassestests/packagespasses (or the packages I touched: libcamera has notest/all)versionbumped, and the new version is in the commit subjectCo-Authored-By:orAssisted-by:trailer, never aSigned-off-by:On the phone
focus_absolute0-4095 (Hall read-back); omacam's autofocus settles on a subject at about 25 cm in a little over a second; a full-size photo (3000x3992) is sharpAflines added by hand to its installeds5kgn8.yaml, which is exactly what 0057 changes. I also haven't checked the far end on a distant scene, the ultrawide or front cameras (no change), or continuous AF over a long session.userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1). The driver writes only the focus target register, from the kernel.tools/phone-smokereportPackages: hyprland 0.57.0-3.1, libcamera 0.7.2-4.22, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamessages 0.2.2-1, omamobile-apps 0.2.2-1, omamobile-device-tegu 0.2.9-1, omamobile-firstboot 0.1.3-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.32-1, omamobile-owl-widgets 0.1.2-1, omamobile-shell 0.2.100-1, omamobile-voice 0.1.0-1, omaphone 0.2.3-1, omarchy 4.0.6-1, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1
(
sound cards,sensorsandcamerasskip on this phone: no audio/AoC setup on this install, and no libcamera tools installed.)The changes were written with an AI assistant (Claude). I tested them on my phone.
🤖 Generated with Claude Code