On Wed, Apr 18, 2018 at 03:47:33PM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Fri, Mar 16, 2018 at 9:39 AM, Simon Horman wrote:
> > On Tue, Mar 13, 2018 at 08:23:05PM +0100, Geert Uytterhoeven wrote:
> >> On Tue, Mar 13, 2018 at 7:49 PM, Simon Horman wrote:
> >> > On Mon, Mar 12, 2018 a
Hi Simon,
On Fri, Mar 16, 2018 at 9:39 AM, Simon Horman wrote:
> On Tue, Mar 13, 2018 at 08:23:05PM +0100, Geert Uytterhoeven wrote:
>> On Tue, Mar 13, 2018 at 7:49 PM, Simon Horman wrote:
>> > On Mon, Mar 12, 2018 at 04:11:57PM +0100, Geert Uytterhoeven wrote:
>> >> On Renesas R-Car Gen2 SoCs,
On Tue, Mar 13, 2018 at 08:23:05PM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Tue, Mar 13, 2018 at 7:49 PM, Simon Horman wrote:
> > On Mon, Mar 12, 2018 at 04:11:57PM +0100, Geert Uytterhoeven wrote:
> >> On Renesas R-Car Gen2 SoCs, the pin group for the MDIO bus is named
> >> "mdio".
>
Hi Simon,
On Tue, Mar 13, 2018 at 7:49 PM, Simon Horman wrote:
> On Mon, Mar 12, 2018 at 04:11:57PM +0100, Geert Uytterhoeven wrote:
>> On Renesas R-Car Gen2 SoCs, the pin group for the MDIO bus is named
>> "mdio".
>>
>> When initial support was added for R-Car H3, the MDIO pin was forgotten,
>>
On Mon, Mar 12, 2018 at 04:11:57PM +0100, Geert Uytterhoeven wrote:
> Hi Simon, Magnus,
>
> On Renesas R-Car Gen2 SoCs, the pin group for the MDIO bus is named
> "mdio".
>
> When initial support was added for R-Car H3, the MDIO pin was forgotten,
> and the MDC pin got its own group named "m