Ethernet device with shared mdio

[Mike Belanger]

The following device tree specifies a shared mdio.
The ffec driver uses miibus.
When there is a shared mdio, one of the device instances will not be able to 
properly configure the PHY, as it needs to use the other devices resource to 
read/write the PHY.

&fec1 {
                pinctrl-names = "default";
                pinctrl-0 = <&pinctrl_fec1>;
                phy-mode = "rgmii-id";
                phy-handle = <&ethphy0>;
                fsl,magic-packet;
                status = "okay";

                mdio {
                                #address-cells = <1>;
                                #size-cells = <0>;

                                ethphy0: ethernet-phy@0 {
                                                compatible = 
"ethernet-phy-ieee802.3-c22";
                                                reg = <0>;
                                };

                                ethphy1: ethernet-phy@1 {
                                                compatible = 
"ethernet-phy-ieee802.3-c22";
                                                reg = <1>;
                                };
                };
};

&fec2 {
                pinctrl-names = "default";
                pinctrl-0 = <&pinctrl_fec2>;
                phy-mode = "rgmii-txid";
                phy-handle = <&ethphy1>;
                phy-supply = <&reg_fec2_supply>;
                nvmem-cells = <&fec_mac1>;
                nvmem-cell-names = "mac-address";
                rx-internal-delay-ps = <2000>;
                fsl,magic-packet;
                status = "okay";
};

Does FreeBSD have any plans for supporting hardware that specifies a shared 
mdio in the dtb?
Just knowing the general approach being considered would be helpful.

----------------------------------------------------------------------
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.