include/linux/mdio-mux.h
Source file repositories/reference/linux-study-clean/include/linux/mdio-mux.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/mdio-mux.h- Extension
.h- Size
- 1021 bytes
- Lines
- 33
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/device.hlinux/phy.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef __LINUX_MDIO_MUX_H
#define __LINUX_MDIO_MUX_H
#include <linux/device.h>
#include <linux/phy.h>
/* mdio_mux_init() - Initialize a MDIO mux
* @dev The device owning the MDIO mux
* @mux_node The device node of the MDIO mux
* @switch_fn The function called for switching target MDIO child
* mux_handle A pointer to a (void *) used internaly by mdio-mux
* @data Private data used by switch_fn()
* @mux_bus An optional parent bus (Other case are to use parent_bus property)
*/
int mdio_mux_init(struct device *dev,
struct device_node *mux_node,
int (*switch_fn) (int cur, int desired, void *data),
void **mux_handle,
void *data,
struct mii_bus *mux_bus);
void mdio_mux_uninit(void *mux_handle);
#endif /* __LINUX_MDIO_MUX_H */
Annotation
- Immediate include surface: `linux/device.h`, `linux/phy.h`.
- Atlas domain: Core OS / Core Kernel Interface.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.