True. I picked the port type properties that are interpreted by
phylink. Basically, I think that everything that's described in:
devicetree/bindings/net/ethernet-controller.yaml
is valid for the ACPI as well
So you are saying ACPI is just DT stuff into tables? Then why bother
with ACPI? Just use DT.
Right, O.K. Please document anything which phylink already supports:
hylink.c: ret = fwnode_property_read_u32(fixed_node, "speed", &speed);
phylink.c: if (fwnode_property_read_bool(fixed_node, "full-duplex"))
phylink.c: if (fwnode_property_read_bool(fixed_node, "pause"))
phylink.c: if (fwnode_property_read_bool(fixed_node, "asym-pause"))
phylink.c: ret = fwnode_property_read_u32_array(fwnode, "fixed-link",
phylink.c: ret = fwnode_property_read_u32_array(fwnode, "fixed-link",
phylink.c: if (dn || fwnode_property_present(fwnode, "fixed-link"))
phylink.c: if ((fwnode_property_read_string(fwnode, "managed", &managed) == 0 &&
If you are adding new properties, please do that In a separate patch,
which needs an ACPI maintainer to ACK it before it gets merged.
Andrew