Documentation/devicetree/bindings/net/icplus-ip101ag.txt
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/net/icplus-ip101ag.txt
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/net/icplus-ip101ag.txt- Extension
.txt- Size
- 650 bytes
- Lines
- 20
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: documentation
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
IC Plus Corp. IP101A / IP101G Ethernet PHYs
There are different models of the IP101G Ethernet PHY:
- IP101GR (32-pin QFN package)
- IP101G (die only, no package)
- IP101GA (48-pin LQFP package)
There are different models of the IP101A Ethernet PHY (which is the
predecessor of the IP101G):
- IP101A (48-pin LQFP package)
- IP101AH (48-pin LQFP package)
Optional properties for the IP101GR (32-pin QFN package):
- icplus,select-rx-error:
pin 21 ("RXER/INTR_32") will output the receive error status.
interrupts are not routed outside the PHY in this mode.
- icplus,select-interrupt:
pin 21 ("RXER/INTR_32") will output the interrupt signal.Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
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.