Repository navigation
arm64: dts: exynos: bluejay: describe the disabled PCIe Wi-Fi path - #230
Conversation
|
Thanks, Chris — everything new is disabled and the shared dtsi only gains labels, which is what I'd hoped. This one simply waits on #227; once that's in, please rebase so only your two commits remain, and we'll let CI run the binding checks. |
a453f29 to
8b6ab24
Compare
8b6ab24 to
4cb0149
Compare
|
November 13 staged DT runtime result: Tested signed integration: The staged overlays enabled the submitted disabled descriptions in order: w0 pool only; w1 pool plus WLAN regulator, PHY and PCIe with the endpoint unbound; w2 the matched endpoint policy and provisioned station firmware. The pool was 64 MiB at The merge order is unchanged: #227 and #228 first, then rebase this PR to its two own commits and rerun CI. No dependency rebase or source change was made for this report. These were attended headless stages with storage guards, a PID-1-owned 20-second watchdog, host logging and fresh SSH postchecks. They do not qualify the revised desktop/GPU path, native panel modesetting, suspend, endurance or a release installer. The historical graphical desktop has been restored. No kernel commit or DCO metadata changed; |
|
Thank you, Chris. The staged run (pool, then the link, then the station) is the order I'd want, and everything new in this tree is disabled. The two labels in One thing for the omarchy-mobile side: main's |
|
The mobile overlay follow-up #777 has merged, and the unchanged tested integration This PR remains draft until #227 and #228 land. Then I will rebase it to its two own commits, retain |
Allow the BCM4389 PCI identity together with the existing fullmac fallback. Other compatible forms retain their existing schema. Assisted-by: LLM Signed-off-by: Chris Gray <chrisgray70@gmail.com>
Describe the GS101 PCIe1/PHY path, restricted DMA pool and BCM4389 endpoint. All new hardware and the WL_REG_ON regulator remain disabled. PCI power control consumes the root-port regulator and its 200 ms delay; the host no longer owns an endpoint enable GPIO. The endpoint requests the confined DMA path, packet limit and provisioned ASCII MAC explicitly. Depends on the GS101 PCIe/PHY and brcmfmac policy topics. The current source is not the exact tested development stack and has not been booted. A future gated overlay must also enable the WL_REG_ON regulator. Assisted-by: LLM Signed-off-by: Chris Gray <chrisgray70@gmail.com>
4cb0149 to
9effb03
Compare
|
Thank you, Chris. Everything I asked for is done: #227 and #228 are in, the branch is down to your two commits, CI is green on this head (with dtbs_check and dt_binding_check), #777 has the overlays as they ran, and One note for the record: the only line that is live on bluejay before any overlay is If you'd like to, you could drop the "Depends on …" and "has not been booted" sentences from the DTS commit message before I merge, since both are out of date now. Otherwise I'll merge it as it is. |
Describe the BCM4389 PCI identity/fallback and disabled Bluejay PCIe Wi-Fi hardware in two commits. WL_REG_ON is a disabled fixed regulator consumed through PCI power control; endpoint properties request restricted DMA, the qualified packet limit and provisioned ASCII MAC handling. The DMA pool and all new hardware nodes stay disabled.
#227 and #228 have merged. This PR is now reduced to its two own commits on current
omamobile(317d87dc2), as requested. The board file retains both includes in the requested order:gs101-bluejay-input.dtsi, thengs101-bluejay-wifi.dtsi. Existing human author sign-offs and assistance trailers are retained.Validation
9effb0347. The binding change is unchanged; the DT patch differs from the prior submission only in include context/order needed alongside the merged input description.9effb03478c77ebd97c851bafc0c38b2a41dcfb4.Saved staged runtime evidence
The November 12–13 Pixel 6a run used signed integration 720a495233734e4328a09c33c095d72a8291e1c4, kernel
7.3.0-rc6-omamobile-bluejay-review-20261111, with matching Image, stage DTs and modules. This is an integration result containing the submitted changes.The overlays enabled the disabled descriptions in order: w0 pool only; w1 pool plus WLAN regulator, PHY and PCIe with the endpoint unbound; w2 the matched endpoint policy and provisioned station firmware. The pool was 64 MiB at
0xc4000000; PCIe linked on try 1 to14e4:4441; the driver verified restricted DMA below 4 GiB, and managed-station DHCP plus interface-bound HTTPS returned 200. The link-stage overlay enabledregulator-wlan. Submitted base nodes remain disabled.These were attended headless stages with storage guards, a PID-1-owned 20-second watchdog, host logging and fresh SSH postchecks. They do not establish reference-device regression, suspend, endurance or installer qualification.
AUTO_WRITE=noand masked automatic boot-success remain in force.The unchanged tested integration is preserved on bringup/bluejay-reviewed-tested-20261111. The matching mobile overlay source follow-up omarchy-mobile #777 has merged. Its source comparison matches the saved trial DTs; no boot of the newly published overlay file is claimed.
No firmware, private captures, credentials, handset identifiers or calibration data are submitted.