Proposing Common PHY Framework in Zephyr
summary
Proposal implements a Linux-like common PHY framework inside Zephyr that actually binds separate PHY drivers to controller drivers via device tree, provides concrete APIs (PHY ops: init/exit/power on/power off/reset/calibrate), and exposes phi_create/phy_get and a phy core to register and reference PHY instances. It targets external PHYs used by USB PCIe CSI and Ethernet, separates PHY code from controllers to remove duplication, and ships sample PHY and controller driver code showing the framework in use.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:24Agenda
- 1:53PHY: An Introduction
- 3:43Functions of a PHY
- 5:47PHY In A System
- 7:17Existing ways to Implement PHY
- 8:36Need of A Generic PHY framework
- 9:22Proposed PHY framework
- 11:57PHY Framework Implementation
- 12:46Binding
- 18:13PHY ops
- 19:12PHY init
- 22:12PHY operations
- 23:28Creating the PHY
- 24:47PHY get
- 27:13Sample PHY driver
- 29:17Sample Controller Driver
- 31:00Conclusion and Future Scope
related talks
45mBluetooth Low Energy Controller in Zephyr OS
40mHow to extract a bare metal flavor of code out of Zephyr to use in RTOS?
23mA Dive into Zephyr Device Driver Model
41mZephyr & Linux Devicetree, Similarities and Differences – Practical Guide To Boards, Shields and Con
45mBluetooth Low Energy Controller in Zephyr OS
40mReworking the Zephyr Clock Control Subsystem
45mUSB Support in Zephyr OS
33mImproving System Configuration for Zephyr and Beyond