summaryrefslogtreecommitdiff
path: root/programs/fuzz/corpuses/server
diff options
context:
space:
mode:
authorTom Rini <[email protected]>2026-07-14 15:41:13 -0600
committerTom Rini <[email protected]>2026-07-14 15:41:13 -0600
commit21ee6442ed165114c42276348b02d40f5710a577 (patch)
tree3ee0d08b860e3db997d78b968c74d233e0ddb1ab /programs/fuzz/corpuses/server
parent501d76ca801343cce6dafb17740a8b679ed17072 (diff)
parent02d74afe94a5510312d01ad79a3801c589cb6a20 (diff)
Merge patch series "pinctrl: aspeed: Add AST2700 pinctrl drivers"
Billy Tsai <[email protected]> says: The AST2700 is Aspeed's 7th-generation BMC SoC with a dual-die architecture: SoC0 (CPU die) and SoC1 (I/O die) each have their own SCU with independent multi-function pin controls. Initial AST2700 platform support is already merged in next, including the ast2700.dtsi pinctrl0 and pinctrl1 nodes, but no pinctrl driver backs them yet. This series adds one pinctrl driver per die, each followed by a patch adding its pin configuration support. Both drivers use the generic pinctrl framework and are compatible with the Linux kernel device tree bindings, using the same group and function names as the Linux aspeed,ast2700-soc0/soc1-pinctrl drivers so pin states can be shared between the kernel and U-Boot device trees. Patch 1 adds the SoC0 driver, which models each (function, group) pair as a flat register mask/value table covering eMMC, VB, VGA DDC, JTAG master port select, PCIe RC PERST and USB2/USB3 port routing. Patch 2 adds SoC0 pin configuration support: every GPIO18A/GPIO18B ball has its own IO control register providing a 3 mA to 41 mA drive strength selector and bias control. Patch 3 adds the SoC1 driver, porting the per-pin 4-bit multi-function selector scheme (220 pins, 238 groups, 217 functions) together with the virtual pins for PCIe RC2 PERST, the USB2 port C/D mode and SGMII controls. Patch 4 adds SoC1 pin configuration support: a per-pin bias enable bit and sparse 2-bit drive strength fields (4 mA to 16 mA in 4 mA steps) mirroring the Linux driver layout. The bias-disable, bias-pull-down, bias-pull-up and drive-strength properties can be applied per pin or per group. Both drivers implement gpio_request_enable so the GPIO driver can reclaim pins through the gpio-ranges already present in ast2700.dtsi, and provide get_pin_muxing so "pinmux status" reports the active signal of every pin. Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'programs/fuzz/corpuses/server')
0 files changed, 0 insertions, 0 deletions