summaryrefslogtreecommitdiff
path: root/src/drivers/net/atl1e.c
diff options
context:
space:
mode:
authorMario Scheithauer <mario.scheithauer@siemens.com>2022-11-02 15:57:10 +0100
committerMartin L Roth <gaumless@gmail.com>2022-11-24 05:53:55 +0000
commit67f63e768d8860ebc6bae5987e2d928efabcf7c4 (patch)
tree79b4434bbc318750dc4e3ba45436277aefb27c27 /src/drivers/net/atl1e.c
parent66e44e325278f8a4b4227eb7d1c5d6c56e1686cd (diff)
src/device + util/sconfig: Introduce new device 'mdio'
This patch extends the available device paths with a new device 'mdio'. MDIO is the 'Management Data Input/Output' called interface which is used to access an Ethernet PHY behind a MAC to change settings. The real payload data path is not handled by this interface. To address the PHY correctly on the MDIO bus, there is a 5 bit address needed, which often can be configured via pins on the mainboard. Therefore, the new introduced device has an 'addr' field to define its address. If one wants to use a MDIO device in devicetree, the syntax is straight forward (example): device mdio 0x2 on end As the MDIO interface is driven by the MAC, most likely this MDIO device will be hooked in as a child device of the (PCI attached) MAC device. With the new introduced ops_mdio a new interface is added to provide an API for read and write access over MDIO. Change-Id: I6691f92c4233bc30afc9029840b06f74bb1eb4b2 Signed-off-by: Mario Scheithauer <mario.scheithauer@siemens.com> Signed-off-by: Werner Zeh <werner.zeh@siemens.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/69382 Reviewed-by: Angel Pons <th3fanbus@gmail.com> Reviewed-by: Arthur Heymans <arthur@aheymans.xyz> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/drivers/net/atl1e.c')
0 files changed, 0 insertions, 0 deletions