From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Geert Uytterhoeven" <geert+renesas@glider.be>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: sh-pfc: r8a7796: Add group for AVB MDIO and MII pins
Date: Thu, 20 Apr 2017 13:18:01 +0300 [thread overview]
Message-ID: <2338736.vqmUpXt7la@avalon> (raw)
In-Reply-To: <CAMuHMdWYWWVuFWz7kULLbZeOxVAssFQ584cO45THrLQ6FwTYSA@mail.gmail.com>
Hi Geert,
On Thursday 20 Apr 2017 12:11:41 Geert Uytterhoeven wrote:
> On Thu, Apr 20, 2017 at 12:02 PM, Laurent Pinchart wrote:
> > On Thursday 20 Apr 2017 11:49:06 Geert Uytterhoeven wrote:
> >> Group the AVB pins into similar groups as found in other sh-pfc drivers.
> >> The pins can not be muxed between functions other than AVB, but their
> >> drive strengths can be controlled.
> >>
> >> The group avb_mdc containing ADV_MDC and ADV_MDIO is called avb_mdio on
> >> other SoCs. In pfc-r8a7796 the avb_mdc group already existed and is in
> >> use in DT. Therefore add the ADV_MDIO pin to the existing group instead
> >> of renaming it.
> >
> > This clearly shows that we need a few kernel releases to test PFC-related
> > code and DT before we can commit to an ABI. How do you think we should
> > handle this ?
>
> That's a difficult question ;-)
>
> For now I'd like to treat R-Car M3-W the same as H3.
I still believe we should introduce some kind of unstable period for DT
bindings, during which they will be merged in mainline but still subject to
modification. It could just be a few kernel releases.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-04-20 10:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 9:49 [PATCH] pinctrl: sh-pfc: r8a7796: Add group for AVB MDIO and MII pins Geert Uytterhoeven
2017-04-20 10:02 ` Laurent Pinchart
2017-04-20 10:11 ` Geert Uytterhoeven
2017-04-20 10:18 ` Laurent Pinchart [this message]
2017-04-20 11:40 ` Geert Uytterhoeven
2017-04-20 11:44 ` Laurent Pinchart
2017-04-20 11:47 ` Geert Uytterhoeven
2017-05-02 14:33 ` Niklas Söderlund
2017-05-11 8:49 ` Geert Uytterhoeven
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=2338736.vqmUpXt7la@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).