On Thursday 07 April 2016 03:17 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Friday 25 March 2016 07:39 AM, Simon Horman wrote:
>> On Mon, Mar 07, 2016 at 10:58:39AM +0900, Simon Horman wrote:
>>> Add fallback compatibility strings for rcar phy drivers.
>>>
>>> In the case of Renesas R-Car har
Hi,
On Friday 25 March 2016 07:39 AM, Simon Horman wrote:
> On Mon, Mar 07, 2016 at 10:58:39AM +0900, Simon Horman wrote:
>> Add fallback compatibility strings for rcar phy drivers.
>>
>> In the case of Renesas R-Car hardware we know that there are generations of
>> SoCs, e.g. Gen 2 and Gen 3. But
On Mon, Mar 07, 2016 at 10:58:39AM +0900, Simon Horman wrote:
> Add fallback compatibility strings for rcar phy drivers.
>
> 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 bl
Add fallback compatibility strings for rcar phy drivers.
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
