Repository navigation
arm64: dts: exynos: gs101-raven: add the rear flash LED - #113
Conversation
|
Thanks. I checked the node against stock's One small thing before I merge: the DT commit's subject is |
73bea07 to
176e160
Compare
|
Smoke report from the build that runs this: #112 (comment).
|
176e160 to
c1b3b11
Compare
|
Thanks, the DT commit now says The branch is on today's For future raven DT PRs: stacking them (each on the previous one's branch) saves a rebase round each time, since they all add at the end of the same file. |
The Pixel 6 Pro's rear flash LED is an LM3644TT on I2C 7, driven by the same torch-only driver as the Pixel 7's. Say so in the help text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: saiththerobo <the.tom.sharp@gmail.com>
The Pixel 6 Pro's rear flash LED driver is a TI LM3644 at 0x63 on I2C 7 (USI7), with its HWEN on gpp23-6, as stock's raven device tree describes it. Torch only, capped at 50 mA per channel (a bring-up limit). Tested on raven (7.3.0-rc6): the driver reads the LM3644TT (device ID 0x04) and offers 17 torch steps, 2550-49110 uA per channel; the LED turns on and off by hand and from the shell's torch tile (brightnessctl through logind, no udev rule needed). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: saiththerobo <the.tom.sharp@gmail.com>
c1b3b11 to
f5e6ff7
Compare
|
Thanks for the rebase. I checked the new push against what we discussed:
Nothing more is needed on your side. I'll merge it as it stands. |
The matrix after the merges since #118, with each cell going by the merged notes: - Pixel 7 (panther): the board file (derekross/linux-omarchy-mobile#108) and the FT3658 touch driver (derekross/linux-omarchy-mobile#109) have merged into the published kernel, so Boot, Storage, Buttons and USB net say "in the published kernel" instead of "in review". Touch stays "no": the driver and the touch rails are published, but the board file has no touch node, and panther's notes end at boot 8 with the controller not answering. BRINGUP-M1's status and NOTES' header say the same. - Pixel 6 Pro (raven), Charging: no -> works. device-raven 0.1.26 (#112, #126) loads the MAX77759 charger at boot with its temperature guard; USB-PLAN section 4 records C0-C5 passed on 2026-10-28, a full charge to 100 % included. The battery node is derekross/linux-omarchy-mobile#112; the runs were on an unpublished integration kernel, and the cell says so. - raven, Torch: still works; the LED's node is now in the published kernel (derekross/linux-omarchy-mobile#113), tested on omamobile-gs101-torch and not yet run from the published kernel. - Pixel 9a (tegu), Fingerprint: no -> WIP. FINGERPRINT-PLAN records F0 and F2-F6b passed on an unpublished kernel: Trusty's TA runs and the HAL sees the sensor; enrollment waits for the factory calibration (F6c). omamobile-fingerprint 0.1.10 (#101) maps Trusty's stores for it. Left as they were: tegu's Charging (the MAX77779 charger driver, derekross/linux-omarchy-mobile#92, is published, but tegu's notes record no run of it), the gs201 HSI2 pin controller (derekross/linux-omarchy-mobile#123, no cell), felix (#35 is a plan) and cheetah (nothing merged for it). Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The Pixel 6 Pro's rear flash LED driver is the same TI LM3644TT as the Pixel 7 Pro's, so cheetah's torch-only
leds-lm3644driver covers it.Tested on raven (7.3.0-rc6): the driver reads the LM3644TT (device ID 0x04) and offers 17 torch steps, 2550–49110 µA per channel. The LED turns on and off by hand and from the shell's torch tile (brightnessctl through logind, no udev rule needed).
tools/kernel-pr-checkpasses with--build;dt-validatereports nothing new; the 4 checkpatch warnings are theCo-Authored-By:trailer, as in #8.🤖 Generated with Claude Code