Fixed PHY problems

[Joakim Tjernlund]

On Fri, 2007-05-11 at 18:04 +0400, Vitaly Bordug wrote:
> > hmm, been trying to figure out all day how to make ucc_geth find my
> > fixed PHY without success. OF experts, please give me some hints.
> > My board is derived from the in tree mpc832x_mds bord and I am trying to
> > convert this part:
> > 	mdio at 2320 {
> > 			#address-cells = <1>;
> > 			#size-cells = <0>;
> > 			reg = <2320 18>;
> > 			device_type = "mdio";
> > 			compatible = "ucc_geth_phy";
> > 
> > 			phy3: ethernet-phy at 03 {
> > 				interrupt-parent = < &ipic >;
> > 				interrupts = <11 8>;
> > 				reg = <3>;
> > 				device_type = "ethernet-phy";
> > 			};
> > 			phy4: ethernet-phy at 04 {
> > 				interrupt-parent = < &ipic >;
> > 				interrupts = <12 8>;
> > 				reg = <4>;
> > 				device_type = "ethernet-phy";
> > 			};
> > 		};
> > into fixed PHYs, how do I do that?
> 
> Well, fixed phy didn't made it to have any representation in dts as of now, at least
> what I am aware of, and it is just a platform device so far.
> 
> Speaking about it, I am recalling long-pending enhancement to unify fixed interface with
> bus_id representation in gianfar (that is having numeric bus:device way).
> 
> About dts, the only options fixed phy can have, are speed and duplex, it does not trigger irq and
> so on, and I see something like 
> 
> phy1: fixed-phy at 01 {
> 	reg = <100 1>; /*100Mps, full duplex*/
> 	device_type = "ethernet-phy";
> };

Looks resonable to me, although I think reg needs to be <d#100 1>

How do make ucc_geth find it?

PS.
   Could you send me the patch that fixes:
Device 'fixed at 100:1' does not have a release() function, it is broken
and must be fixed.

Is this warning harmless?