Re: [PATCH 0/3] arm64: dts: renesas: Rename EtherAVB "mdc" pin group to "mdio"

2018-04-24 Thread Simon Horman
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 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,
> >> >> and the MDC pin got its own group named "mdc".  During the addition of
> >> >> support for R-Car M3-W, this mistake was noticed.  But as R-Car H3 and
> >> >> M3-W are pin compatible, and can be mounted on the same boards, the
> >> >> decision was made to just add the MDIO pin to the existing "mdc" group.
> >> >> Later this was extended to R-Car H3 ES2.0, and M3-N, because of pin
> >> >> compatibility, and to R-Car D3, in the name of consistency among R-Car
> >> >> Gen3 SoCs.
> >> >>
> >> >> However, this decision keeps on being questioned when adding new SoC
> >> >> support.  Hence bite the bullet and admit our mistake, and rename the
> >> >> pin group from "mdc" to "mdio", like on R-Car Gen2 SoCs.
> >> >>
> >> >> This series is the DTS part, and depends on the series '[PATCH 0/6]
> >> >> pinctrl: sh-pfc: rcar-gen3: Rename EtherAVB "mdc" pin group to "mdio"'.
> >> >
> >> > could you comment on the forwards/backwards compatibility considerations
> >> > of this series?
> >>
> >> Old and new kernels work with old DT (tested on Salvator-X(S).
> >> New DT requires a new kernel, hence the dependency of the DTS part on the
> >> driver part.
> >
> > Thanks, that is fine by me.
> >
> > I have marked these patches as deferred. Please repost or ping me
> > once the dependency is available in an RC release.
> 
> Now in v4.17-rc1.

Thanks, applied.


Re: [PATCH 0/3] arm64: dts: renesas: Rename EtherAVB "mdc" pin group to "mdio"

2018-04-18 Thread Geert Uytterhoeven
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, 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 "mdc".  During the addition of
>> >> support for R-Car M3-W, this mistake was noticed.  But as R-Car H3 and
>> >> M3-W are pin compatible, and can be mounted on the same boards, the
>> >> decision was made to just add the MDIO pin to the existing "mdc" group.
>> >> Later this was extended to R-Car H3 ES2.0, and M3-N, because of pin
>> >> compatibility, and to R-Car D3, in the name of consistency among R-Car
>> >> Gen3 SoCs.
>> >>
>> >> However, this decision keeps on being questioned when adding new SoC
>> >> support.  Hence bite the bullet and admit our mistake, and rename the
>> >> pin group from "mdc" to "mdio", like on R-Car Gen2 SoCs.
>> >>
>> >> This series is the DTS part, and depends on the series '[PATCH 0/6]
>> >> pinctrl: sh-pfc: rcar-gen3: Rename EtherAVB "mdc" pin group to "mdio"'.
>> >
>> > could you comment on the forwards/backwards compatibility considerations
>> > of this series?
>>
>> Old and new kernels work with old DT (tested on Salvator-X(S).
>> New DT requires a new kernel, hence the dependency of the DTS part on the
>> driver part.
>
> Thanks, that is fine by me.
>
> I have marked these patches as deferred. Please repost or ping me
> once the dependency is available in an RC release.

Now in v4.17-rc1.

Gr{oetje,eeting}s,

Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds


Re: [PATCH 0/3] arm64: dts: renesas: Rename EtherAVB "mdc" pin group to "mdio"

2018-03-16 Thread Simon Horman
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".
> >>
> >> When initial support was added for R-Car H3, the MDIO pin was forgotten,
> >> and the MDC pin got its own group named "mdc".  During the addition of
> >> support for R-Car M3-W, this mistake was noticed.  But as R-Car H3 and
> >> M3-W are pin compatible, and can be mounted on the same boards, the
> >> decision was made to just add the MDIO pin to the existing "mdc" group.
> >> Later this was extended to R-Car H3 ES2.0, and M3-N, because of pin
> >> compatibility, and to R-Car D3, in the name of consistency among R-Car
> >> Gen3 SoCs.
> >>
> >> However, this decision keeps on being questioned when adding new SoC
> >> support.  Hence bite the bullet and admit our mistake, and rename the
> >> pin group from "mdc" to "mdio", like on R-Car Gen2 SoCs.
> >>
> >> This series is the DTS part, and depends on the series '[PATCH 0/6]
> >> pinctrl: sh-pfc: rcar-gen3: Rename EtherAVB "mdc" pin group to "mdio"'.
> >
> > could you comment on the forwards/backwards compatibility considerations
> > of this series?
> 
> Old and new kernels work with old DT (tested on Salvator-X(S).
> New DT requires a new kernel, hence the dependency of the DTS part on the
> driver part.

Thanks, that is fine by me.

I have marked these patches as deferred. Please repost or ping me
once the dependency is available in an RC release.


Re: [PATCH 0/3] arm64: dts: renesas: Rename EtherAVB "mdc" pin group to "mdio"

2018-03-13 Thread Geert Uytterhoeven
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,
>> and the MDC pin got its own group named "mdc".  During the addition of
>> support for R-Car M3-W, this mistake was noticed.  But as R-Car H3 and
>> M3-W are pin compatible, and can be mounted on the same boards, the
>> decision was made to just add the MDIO pin to the existing "mdc" group.
>> Later this was extended to R-Car H3 ES2.0, and M3-N, because of pin
>> compatibility, and to R-Car D3, in the name of consistency among R-Car
>> Gen3 SoCs.
>>
>> However, this decision keeps on being questioned when adding new SoC
>> support.  Hence bite the bullet and admit our mistake, and rename the
>> pin group from "mdc" to "mdio", like on R-Car Gen2 SoCs.
>>
>> This series is the DTS part, and depends on the series '[PATCH 0/6]
>> pinctrl: sh-pfc: rcar-gen3: Rename EtherAVB "mdc" pin group to "mdio"'.
>
> could you comment on the forwards/backwards compatibility considerations
> of this series?

Old and new kernels work with old DT (tested on Salvator-X(S).
New DT requires a new kernel, hence the dependency of the DTS part on the
driver part.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds


Re: [PATCH 0/3] arm64: dts: renesas: Rename EtherAVB "mdc" pin group to "mdio"

2018-03-13 Thread Simon Horman
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 "mdc".  During the addition of
> support for R-Car M3-W, this mistake was noticed.  But as R-Car H3 and
> M3-W are pin compatible, and can be mounted on the same boards, the
> decision was made to just add the MDIO pin to the existing "mdc" group.
> Later this was extended to R-Car H3 ES2.0, and M3-N, because of pin
> compatibility, and to R-Car D3, in the name of consistency among R-Car
> Gen3 SoCs.
> 
> However, this decision keeps on being questioned when adding new SoC
> support.  Hence bite the bullet and admit our mistake, and rename the
> pin group from "mdc" to "mdio", like on R-Car Gen2 SoCs.
> 
> This series is the DTS part, and depends on the series '[PATCH 0/6]
> pinctrl: sh-pfc: rcar-gen3: Rename EtherAVB "mdc" pin group to "mdio"'.

Hi Geert,

could you comment on the forwards/backwards compatibility considerations
of this series?