From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] documentation: Fix pinctrl documentation for Meson8 / Meson8b
Date: Fri, 25 Mar 2016 08:40:20 -0500 [thread overview]
Message-ID: <20160325134020.GA15177@rob-hp-laptop> (raw)
In-Reply-To: <CAL9uMOGaf5556KX5RJWbaW0d1zcTZu4S6FvoqEXQCWXg1QUDpg@mail.gmail.com>
On Wed, Mar 23, 2016 at 05:04:19PM +0100, Carlo Caione wrote:
> On Wed, Mar 23, 2016 at 4:20 PM, Rob Herring <robh@kernel.org> wrote:
> > On Wed, Mar 23, 2016 at 10:14:00AM +0100, Carlo Caione wrote:
> >> From: Carlo Caione <carlo@endlessm.com>
> >>
> >> Fix pin controller documentation introducing the new compatibles for
> >> the pinctrl drivers specific for aobus / cbus.
> >>
> >> This is needed because we have changed the pin controller driver: we
> >> have now a single specialized pinctrl driver / compatible for each bus
> >> the controller is attached to, instead of one single driver dealing with
> >> all the controllers we have on different buses.
> >
> > Aren't you breaking compatibility with old DTs here? If so, you need to
> > be clear that you are and why you think that is okay.
>
> Rob,
> It's a bit too late to worry about breaking compatibility since the
> driver changes are already landed in mainline and currently Meson8 and
> Meson8b platforms are broken because of this.
> You can read the whole discussion here [1] and here [2]. Driver and DT
> changes were supposed to go in together but a bit of general
> misunderstanding caused this issue.
My comment was the commit message needs to be clear that you are
breaking compatibility. That was true before part of this went in.
> We decided to break compatibility with the old DTs since the the
> platform support is still in the really early stage so I really don't
> think this is going to cause any problem and we have a lot of good
> reasons to split the pinctrl driver. First of all it makes sense from
> the hardware prospective, since we actually have two different pin
> controllers on two different buses. Splitting the driver allows us to
> introduce in the DTS both CBUS and AOBUS as simple buses. We need a
> clear description of the two buses in the DTS since several devices
> have a different register mapping depending on which bus they are
> attached to. Also as you can read here [3] we want to map the whole
> CBUS as a syscon device to be able to access several registers
> scattered inside CBUS.
>From a quick glance, you mainly needed to keep the old compatible string
in the driver and just ignore ao-bank. Then only what depended on
ao-bank would break. Maybe that's less broken than completely breaking
the pinctrl driver...
Anyway, merge the fix:
Acked-by: Rob Herring <robh@kernel.org>
Rob
next prev parent reply other threads:[~2016-03-25 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 9:13 [PATCH v3 0/2] Split pinctrl device for Meson8 / Meson8b and update docs Carlo Caione
2016-03-23 9:13 ` [PATCH v3 1/2] ARM: dts: amlogic: Split pinctrl device for Meson8 / Meson8b Carlo Caione
2016-03-31 9:40 ` Linus Walleij
2016-03-23 9:14 ` [PATCH v3 2/2] documentation: Fix pinctrl documentation " Carlo Caione
2016-03-23 10:34 ` Andreas Färber
2016-03-23 15:20 ` Rob Herring
2016-03-23 16:04 ` Carlo Caione
2016-03-25 13:40 ` Rob Herring [this message]
2016-03-31 9:38 ` Linus Walleij
2016-03-31 9:41 ` Carlo Caione
2016-03-31 9:42 ` Linus Walleij
2016-03-23 19:12 ` [PATCH v3 0/2] Split pinctrl device for Meson8 / Meson8b and update docs Kevin Hilman
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=20160325134020.GA15177@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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