Repository navigation
arm64: dts: exynos: google: zumapro-tegu: Add Bluetooth - #122
Conversation
|
Booted in this form on the palmtop (round bt2: the integration kernel
|
54ecd48 to
8c02598
Compare
|
Thank you, this is a tidy node. I checked it against Google's GPL DT, which for Bluetooth is the zumapro repository's Three small changes, please:
Two notes on the description: it says "Draft", but the PR isn't one, and it says the DTB builds "on today's This lands after #106 (it's stacked on it) and after the rebase on #80. |
8c02598 to
88accde
Compare
88accde to
20f58cf
Compare
|
All three are in 20f58cf, rebased on #106's new head:
On the description: it's not a draft, and since this morning's rebase it does sit on today's |
|
Thanks, all three are in, and I checked each one against
Apart from the rebase onto #106's new head, this is the only commit in the stack that changed. The stack merges cleanly onto today's Before I merge, I need the boot of this head that you mentioned. One detail matters for it. Blob
You don't need a suspend test for this. Since the pull-down is the only change in the pins, the bt2 results plus this boot are enough. On order: this lands after #106 (and so after #96 and #105). It doesn't conflict with #119 or #118. Small thing: the PR description still says "Google's GPL tegu Bluetooth DT", while the commit now says zumapro. Only the commit lands, so it's cosmetic. |
20f58cf to
76fcc3d
Compare
|
Rebased onto #106's new head (one commit, unchanged). Compiles; checkpatch clean. |
76fcc3d to
6ec07ae
Compare
|
Re-stacked onto #96 as suggested; it picked cleanly with ramoops in omamobile. One commit of its own, the node unchanged. Device tree compiles, checkpatch clean. The boot of this head for the Bluetooth row and the host-wake counts is still owed. |
|
The boot of this head (6ec07ae), with the host-wake pull-down, on the palmtop. It's built the same way as #96's run today: defconfig,
The palmtop is back on its daily kernel. |
|
Thank you, @W4HO-ham. That's everything I asked for on the 29th, from a kernel built from this exact head:
The node is unchanged from the version I checked. The gate passes merged onto today's So it's ready. It lands after #96. Once #96 is in, a |
The Pixel 9a's BCM4383 sits on the APM's UART (USI1, uart18) at 3 Mbaud. BT_REG_ON is gpn8-0 behind the chip's latch, clocked by gpp24-3 (the binding's brcm,ble-dbo-gpios), device wake is gpn9-0 and host wake is gpa5-6 (EINT with a pull-down, as stock's bt_host_wake), as in Google's GPL zumapro Bluetooth device tree that tegu includes. With host wake as its interrupt, hci_bcm runs the controller with runtime PM and lets it wake the system. gpa5 becomes an interrupt controller with its eight EINT SPIs (60-67). Link: https://android.googlesource.com/kernel/devices/google/zumapro/+/8831630eee2ad095b85ed452944e6353940966a5/dts/zumapro-board-bluetooth_wakectrl.dtsi Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
6ec07ae to
bea4466
Compare
|
Thanks, @W4HO-ham. The rebase changed only the base: the commit is the same patch as |
Stacked on #106 (the DT stack); only the last commit is new. It booted in this form on the palmtop before the review changes (round bt2, below); the host-wake pull-down is new since, and a boot of this head follows.
The 9a's BCM4383 (driver: kernel #94, merged) sits on the APM's UART (USI1,
uart18) at 3 Mbaud:brcm,ble-dbo-gpios, from Bluetooth: hci_bcm: Add the BCM4383 and its REG_ON latch (Pixel 9a) #94's binding).The pins and values follow Google's GPL tegu Bluetooth DT and match what runs on the palmtop: hci0 up, BlueZ, A2DP, host wake.
Checks: checkpatch --strict clean;
zumapro-tegu.dtbbuilds with W=1 on today'somamobilewith the stack (rebased 2026-10-28 evening). The bt2 run used the integration tree'sdrivers/bluetooth/hci_bcm.cat blob2d46b1da1991e7062a6e4f6555f0d9a7be11b26e, unchanged from that tree's HEAD.