Skip to content

iPod touch 6 (N102): Wi-Fi and Bluetooth (BCM4345B1) - #201

Open
brkosebay wants to merge 16 commits into
OrchardLinux:mainfrom
brkosebay:pr/n102-wireless
Open

brkosebay wants to merge 16 commits into
OrchardLinux:mainfrom
brkosebay:pr/n102-wireless

Conversation

@brkosebay

Copy link
Copy Markdown
Contributor

Stacked on #200 (touch). Review only the last 4 commits.

The iPod touch 6 has a BCM4345B1 combo module ("bacchus"), with Wi-Fi on PCIe and Bluetooth on UART1. The Dialog D2186 PMIC switches the power for both.

Commits

  • kernel: D2186 PMIC GPIOs on the A8 (gpio/0012-0013): apple-d2365 gets the D2186 as match data. It has 21 lines and no interrupt controller yet.
  • kernel: Wi-Fi and Bluetooth on the iPod touch 6.
    • wifi/0011-0012: brcmfmac on PCIe 14e4:43ab, with firmware brcmfmac4345-pcie and CLM. The OTP is read as iOS reads it.
    • pci/0041: pwrctrl-apple-wifi, powered up as for the A8/A8X BCM4350.
    • bluetooth/0008-0009: hci_bcm at 115200 baud, and the TDK module vendor.
    • devices/t7000/0017-0018: UART1, plus the N102's Wi-Fi and Bluetooth nodes from its ADT.
  • kernel: brcmfmac: start the BCM4345 rev 5 firmware (wifi/0013-0014). Without this, the firmware never started ("FW failed to initialize"). brcmfmac loaded every BCM4345 at 0x198000, but the rev 5's RAM starts at 0x1b0000: iOS's chip manager and the firmware's link addresses agree on that. The patch also adds Apple's random seed and its 0xfeedc0de footer before the NVRAM.
  • devices: n102: Wi-Fi works; Bluetooth comes up. The firmware recipe adds the Wi-Fi firmware, NVRAM, CLM and TX-cap blobs from the IPSW, and each module vendor's Bluetooth patchram from BlueTool. Wi-Fi is set to working. Bluetooth input and audio stay untested. The catalog and the matrix are regenerated.

Tested (iPod touch 6)

  • Wi-Fi: firmware BCM4345/5 ... 7.63.79.4 starts and wlan0 comes up. It scans 2.4 and 5 GHz, and the installed system (Omarchy A) joins a network.
  • Bluetooth: hci0 comes up (chip id 81) with BCM.apple,n102-USI.hcd. No device was paired, so input and audio are untested.
  • Flown as one kernel with the storage, touch and battery branches. The storage PR lists how that kernel differs from this head.

Shared code

  • wifi/0013 changes the RAM base only for the BCM4345 below rev 6. The 43455 and 43456 keep 0x198000.
  • The other brcmfmac, pwrctrl and hci_bcm matches are unchanged. The iPad Air 2's BCM4350 was not retested.

Proposed changelog line: "iPod touch 6 (N102): Wi-Fi; Bluetooth controller."

🤖 Generated with Claude Code

The A8's GX6450 runs the same family of firmware as the A9's, so it
becomes a variant of the S8003 chip file rather than a new driver
(drivers/gpu/0063-0073):

- 0063-0064: the S8003 chip described in a variant table, and chip
  hooks for its own GPU ID read and heap table. These touch the A9 and
  A10 paths; their values and functions are unchanged.
- 0065: dt-bindings for apple,t7000-gpu.
- 0066: a GPU node without power domains, and the failing probe step
  named (shared powervr code; nodes with power domains are unchanged).
- 0067-0069: the A8's firmware boot and power up and down in Apple's
  order, compute jobs, and TA/3D render jobs with the parameter-manager
  pool (a8_pm_blocks, a8_pm_grow) and the region-header ring kept in
  the HWRT data set.
- 0070: fault and hang reports and recovery.
- 0071: completion checks in the firmware interrupt's thread, the
  re-check after an early interrupt, a publish that cannot leave a
  failed job in the firmware's ring, Apple's doorbell.
- 0072: a fragment job submitted behind its geometry job, with two
  alternating 3D records (a8_joint, off by default).
- 0073: statistics and the A8's job timeline in debugfs apple_jobs,
  last. It also points the firmware's TA and 3D time words at the
  channel's times; the series without it has not run on the device.

Config: CONFIG_DRM_POWERVR_APPLE goes from unset to =y on apple-4k, as
on apple-16k, so the A8 gets powervr's Apple glue. It builds into the
powervr module on every A7, A8 and A8X kernel; only boards whose device
tree enables an apple,t7000-gpu node bind it.

Assisted-by: LLM
The iPod touch 6 RAM-boots through checkm8, PongoOS and m1n1 to the USB
serial shell. Its descriptor, boot assets and firmware recipe pin the
public iOS 12.5.8 IPSW.

devices/t7000/0011 describes the A8's GPU in t7000.dtsi (the Rogue core,
Fender, the power manager and GPU bridge registers, five interrupts,
the firmware name) and enables it on the N102, where powervr's A8
variant runs Vulkan and OpenGL ES (through Zink) jobs.

Orchard's feature list has no GPU entry and the chip's [gpu] table
records dEQP results, which the A8 does not have yet, so the GPU state
is in devices/n102/README.md. docs/compatibility.md is regenerated.

Assisted-by: LLM
The iPad mini 4 (J96, J97) and the iPhone 6 and 6 Plus (N61, N56) have
the iPod touch 6's A8 GPU. devices/t7000/0012 enables the GPU node in
their shared board files (t7000-mini4.dtsi, t7000-6.dtsi) so people with
these boards can test it; the driver has run only on the iPod touch 6.
Each board's README asks for the probe and ladder results. The A8X
(T7001) has a different GPU and is unchanged.

Assisted-by: LLM
minimal-boot with a constant USB serial number, the kernel's modules,
the GPU firmware and a8-gpu-drm-test, which loads powervr and checks the
probe, Mesa's Vulkan path and two DRM-level replays, each step under a
hardware watchdog with its kernel lines saved. It builds for every A8
board (n102, j96, j97, n61, n56).

tools/extract-fw.py writes the GPU firmware and its border colour table
from Apple's public iPod touch 6 iOS 12.4 IPSW, read over HTTP ranges
with orchard's own IPSW and kernelcache code, or from another IPSW or
kernelcache. Nothing from Apple is in the repository, and everything
build.sh stages is git-ignored.

Assisted-by: LLM
a8-vk-smoke (Vulkan probe, compute, a triangle) and a8-vk-ladder, a set
of Vulkan tests from one clear to vkmark's scenes with every pixel or
value checked on the CPU, both MIT. vk/make-bundle.sh builds them with a
Mesa build of the A8 branch into the self-contained /opt/a8vk bundle
that build.sh's A8_VK_DIR stages, with vkmark when it is installed.

Assisted-by: LLM
The iPod touch 6 keeps its flash behind ANS1 like the iPad Air 2, but
its ANS firmware (iOS 12.4) speaks RTKit 10.2, where the storage
endpoint is 6 instead of 0x20.

- soc-apple/0028: RTKit 10 firmware sends its minor version in the
  HELLO's minimum-version field and wants it back; keep it, answer with
  it and let drivers read the protocol version. RTKit 11 and later are
  unchanged.
- block/0003: asp takes its storage endpoint from the protocol version
  (6 on 10.2, 0x20 on 11 and later); 10.0 is refused by name.
- devices/t7000/0013: the ANS nodes, as Nick Chan wrote them.
- devices/t7000/0014: enabled on the N102 only, ps_ans kept on as the
  boot loader leaves it.

The iPad Air 2 (J81, RTKit 12) runs the same rtkit and asp code; its
path is meant to be unchanged and was not retested.

Assisted-by: LLM
ANS1's write unlock opens the whole controller, so only the driver keeps
writes off the auxiliary namespaces (LLB, firmware, NVRAM, SysCfg with
the factory calibration, ...). Check each command against the ones the
driver uses (identify, the user area's read, write and flush, the write
unlock and the auxiliary reads) before it is queued; anything else,
auxiliary writes and format commands included, is refused.

Shared with the iPad Air 2 (J81), which uses only those commands; not
retested there.

Assisted-by: LLM
With ANS1 on the iPod touch 6, Orchard installs to its user area
(asp0n1) next to a shrunk iOS: storage_read and storage_write are
working. The board now meets every install requirement.

The catalog gets the board's drivers (it had none yet). The ANS1
driver is not one the catalog looks for, so the matrix lists storage as
working with no driver binding, as for the iPad Air 2.

Assisted-by: LLM
The N102's N1 touchscreen on apple_z2, as AppleMultitouchSPIN102 drives
it: the N1 protocol with its C1F58,1 personality and clock settings, its
core supply from a D2186 regulator instead of a GPIO LDO
(input/0030-0031), and the SPI2 node with the Chestnut and D2186
supplies, the touch clock and the calibration alias
(devices/t7000/0015).

Other apple_z2 boards keep their match data; not retested.

Assisted-by: LLM
The N102's DWI backlight drives an LM3534 whose outputs are switched on
over I2C (register 0x10 bit 0, then 600 us), as AppleLMBacklight does
(backlight/0007-0008, devices/t7000/0016). On the T7000 the DWI starts a
transfer with 0x71 in the channel control register, without the extra
send bit (backlight/0006).

backlight/0006 changes the DWI transfer on every T7000 board (iPad mini
4, iPhone 6 and 6 Plus); it was run on the iPod touch 6 only.

Assisted-by: LLM
The firmware recipe makes the touchscreen's firmware
(apple/n102-fwstart.z2fw) from N102.mtprops in the pinned IPSW, with
the C1F58,1 personality and the unit's calibration.

Touch, backlight, the four buttons and the display were seen working on
the iPod touch 6. It has no Touch ID and no cellular modem: none, not
missing.

Assisted-by: LLM
The iPod touch 6's Dialog D2186 PMIC drives Wi-Fi REG_ON (GPIO 10) and
Bluetooth power (GPIO 8). apple-d2365 gets the D2186 as match data: 21
lines with their configuration at 0x400 + 2n and input levels at 0x63,
as AppleD2186PMU reads them. Its PMU event block is not wired, so it is
no interrupt controller, like the D2333.

Other PMICs keep their match data.

Assisted-by: LLM
The N102 has a BCM4345B1 combo module ("bacchus"): Wi-Fi on PCIe port 1,
Bluetooth on UART1.

- wifi/0011-0012: brcmfmac matches the BCM4345 on PCIe (14e4:43ab),
  names its firmware brcmfmac4345-pcie with a CLM blob and reads its OTP
  as iOS does; a missing Apple OTP record falls back to the board type.
- pci/0041: pwrctrl-apple-wifi powers it up like the A8/A8X BCM4350.
- bluetooth/0008-0009: hci_bcm matches the BCM4345B1 at 115200 baud, as
  for the iPad Air 2's BCM4350C2, and knows the TDK module vendor ("t").
- devices/t7000/0017-0018: UART1 for the A8, and the N102's Wi-Fi and
  Bluetooth nodes from its ADT, with REG_ON and Bluetooth power on D2186
  GPIOs 10 and 8.

Other boards' brcmfmac, pwrctrl and hci_bcm matches are unchanged; the
iPad Air 2 (BCM4350) was not retested.

Assisted-by: LLM
The iPod touch 6's BCM4345B1 (rev 5) firmware never started: "FW failed
to initialize". brcmfmac loads every BCM4345 at 0x198000, which is right
for rev 6 and later (43455/43456) but 96 KiB below the rev 5's RAM, which
starts at 0x1b0000 (iOS's AppleBCMWLANChipManagerPCIe4345 and the
firmware's own link addresses agree).

- wifi/0013: 0x1b0000 for BCM4345 below rev 6; 0x198000 otherwise.
- wifi/0014: the 256-byte random seed and 0xfeedc0de footer before the
  NVRAM, which Apple's downloader writes and the firmware's start-up code
  looks for.

The BCM43455/43456 (rev 6 and later) keep 0x198000.

Assisted-by: LLM
The firmware recipe adds the BCM4345B1 module's Wi-Fi firmware, NVRAM,
CLM and TX-cap blobs from the pinned IPSW, and the Bluetooth patchram of
each module vendor (Murata, TDK, USI) from BlueTool.

Wi-Fi was seen working on the iPod touch 6: firmware 7.63.79.4 starts,
it scans 2.4 and 5 GHz and an installed system joins a network.
Bluetooth's controller comes up with the USI patchram; with nothing
paired yet, Bluetooth input and audio stay untested.

Assisted-by: LLM
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant