Re: [PATCH 2/2] phy: rcar-gen3-usb2: add fallback binding

2016-03-02 Thread Geert Uytterhoeven
On Wed, Mar 2, 2016 at 3:37 AM, Simon Horman wrote: > In the case of Renesas R-Car hardware we know that there are generations of > SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the > relationship between IP blocks might be. For example, I believe that

Re: [PATCH 2/2] phy: rcar-gen3-usb2: add fallback binding

2016-03-02 Thread Geert Uytterhoeven
On Wed, Mar 2, 2016 at 3:37 AM, Simon Horman wrote: > In the case of Renesas R-Car hardware we know that there are generations of > SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the > relationship between IP blocks might be. For example, I believe that > r8a7790 is older than

[PATCH 2/2] phy: rcar-gen3-usb2: add fallback binding

2016-03-01 Thread Simon Horman
In the case of Renesas R-Car hardware we know that there are generations of SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the relationship between IP blocks might be. For example, I believe that r8a7790 is older than r8a7791 but that doesn't imply that the latter is a descendant

[PATCH 2/2] phy: rcar-gen3-usb2: add fallback binding

2016-03-01 Thread Simon Horman
In the case of Renesas R-Car hardware we know that there are generations of SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the relationship between IP blocks might be. For example, I believe that r8a7790 is older than r8a7791 but that doesn't imply that the latter is a descendant