Repository navigation
arm64: dts: exynos: google: gs201: add the HSI2 pin controller - #123
Merged
Merged
Conversation
Add the HSI2 pin controller with its GPIO banks gph2 and gph4, as in Google's gs201 device tree (reg 0x14440000, GIC SPI 421, the CMU_HSI2 GPIO clock). The driver already has gs201's HSI2 bank data; the alias pinctrl7 selects it, since pinctrl-samsung picks a controller's entry by its alias and HSI2 is the eighth entry of gs201_pin_ctrl. The Pixel 7a's Bluetooth enable and Wi-Fi power pins (gph2-4, gph2-5) and the PCIe CLKREQ# and PERST# pins sit on this controller. The pin controller stays disabled here; boards that use HSI2 pins enable it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Derek Ross <derekross@gmail.com>
This was referenced Oct 29, 2026
derekross
added a commit
to derekross/omarchy-mobile
that referenced
this pull request
Oct 29, 2026
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds gs201's HSI2 pin controller (
pinctrl@14440000, GIC SPI 421, the CMU_HSI2 GPIO clock) with itsgph2andgph4banks, as in Google's gs201 device tree. The driver already has gs201's HSI2 bank data onomamobile. Thepinctrl7alias selects it, becausepinctrl-samsungpicks a controller's entry by its alias and HSI2 is entry 7 ofgs201_pin_ctrl.The node stays disabled, as PERIC0's does, and boards that use HSI2 pins enable it. The Pixel 7a's Bluetooth (#98) needs it for
gph2-5.Cheetah has run this node, enabled, from
omamobile-intsince 10-11 (with the PCIe nodes in44de4b216269, which this leaves out).Checks
tools/kernel-pr-check --build --merge github/omamobile: merges cleanly, sign-off, prefixes, checkpatch--strict(only theCo-Authored-Bytrailer warnings), and 7 device trees build with W=1 with no new warnings.pinctrl_hsi2/gph2/gph4labels.dt-validate(dtschema 2026.9): the same messages at base and head on every gs201 board, none about the new node.🤖 Generated with Claude Code