On 03/12/2013 01:54 PM, Marc Kleine-Budde wrote: > On 03/12/2013 12:24 PM, Roger Quadros wrote: >> Add clk_rate parameter to platform data. If supplied, the >> NOP phy driver will program the clock to that rate during probe. >> >> Also add 2 flags, needs_vcc and needs_reset. >> If the flag is set and the regulator couldn't be found >> then the driver will bail out with -EPROBE_DEFER. > > Is there a platform which fills out pdata.needs_vcc and > pdata.needs_reset? IMHO it makes no sense to add features for the non DT > case, if there isn't any user for it. > There can be a user in the non DT case as well. Consider the following example: The power regulator that supplies VCC to the PHY device sits over the I2C bus. The NOP transceiver driver is built into the kernel but the regulator driver is built as a module. During boot, the NOP transceiver driver's probe is called before the regulator can be probed. So regulator_get() will fail and if the platform doesn't set the needs_vcc flag, the driver will continue as normal and the PHY device won't work. I know that beagleboard can benefit from this. The current workaround is to register the regulator before we register the PHY in the board file. With the needs_vcc flag, we don't need to have that limitation. cheers, -roger -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
