On Monday, September 19, 2016 10:29:27 AM CEST Kishon Vijay Abraham I wrote:
On Monday 19 September 2016 01:26 AM, Martin Blumenstingl wrote:
quoted
On Fri, Sep 16, 2016 at 10:19 AM, Kishon Vijay Abraham I [off-list ref] wrote:
quoted
quoted
This way the driver will be probed only once (the reset can be done during
probe). The phy driver should scan the dt node and for every sub-node it
invokes phy_create?
I'll recap what we have discussed so far (so you don't have to re-read
the whole thread):
The reference driver treats both USB PHYs as separate devices (the
datasheet has no information about the PHYs though). The only
"special" thing is the shared reset line -> together with Philipp
Zabel (the reset framework maintainer) we decided to make
reset_control_reset work for shared reset lines.
That means we can keep the two PHYs as separate devices inside the
.dts, while keeping everything else separate (just like the reference
driver)
Is this fine for you and Arnd?
yeah.. I'm fine with that.
Agreed, if we don't need to have a device modeled around both
instance, that's ideal.
Arnd