All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 0/3] arm64: dts: renesas: Rename EtherAVB "mdc" pin group to "mdio"
Date: Fri, 16 Mar 2018 09:39:03 +0100	[thread overview]
Message-ID: <20180316083858.bgx56kriezcd5pal@verge.net.au> (raw)
In-Reply-To: <CAMuHMdX8yjx9BaAYpVOhmNfse1rfZ9JYQ__aKQxt73DKoWKdkA@mail.gmail.com>

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 <horms@verge.net.au> 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.

  reply	other threads:[~2018-03-16  8:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 15:11 [PATCH 0/3] arm64: dts: renesas: Rename EtherAVB "mdc" pin group to "mdio" Geert Uytterhoeven
2018-03-12 15:11 ` [PATCH 1/3] arm64: dts: renesas: salvator-common: " Geert Uytterhoeven
2018-03-12 15:11 ` [PATCH 2/3] arm64: dts: renesas: ulcb: " Geert Uytterhoeven
2018-03-12 15:12 ` [PATCH 3/3] arm64: dts: renesas: draak: " Geert Uytterhoeven
2018-03-13 18:49 ` [PATCH 0/3] arm64: dts: renesas: " Simon Horman
2018-03-13 19:23   ` Geert Uytterhoeven
2018-03-16  8:39     ` Simon Horman [this message]
2018-04-18 13:47       ` Geert Uytterhoeven
2018-04-24  9:12         ` Simon Horman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180316083858.bgx56kriezcd5pal@verge.net.au \
    --to=horms@verge.net.au \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.