From: khilman@baylibre•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 4/4] documentation: Fix pinctrl documentation for Meson8 / Meson8b
Date: Fri, 18 Mar 2016 09:59:30 -0700 [thread overview]
Message-ID: <7h7fgzsowd.fsf@baylibre.com> (raw)
In-Reply-To: <CACRpkda3j7oxL0wawkLy-eHnP6zmfmBgKbm7=gTDH1xqXhKKUQ@mail.gmail.com> (Linus Walleij's message of "Tue, 15 Mar 2016 10:10:32 +0100")
Linus Walleij <linus.walleij@linaro•org> writes:
> On Wed, Mar 9, 2016 at 10:41 AM, Carlo Caione <carlo@caione•org> 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.
>>
>> Signed-off-by: Carlo Caione <carlo@endlessm•com>
>> ---
>> Hey Rob,
>> I'm resubmitting a V2 only for this patch since the driver changes have
>> been already taken by Linus.
> (...)
>> Required properties for the root node:
>> - - compatible: "amlogic,meson8-pinctrl" or "amlogic,meson8b-pinctrl"
>> + - compatible: one of "amlogic,meson8-cbus-pinctrl"
>> + "amlogic,meson8b-cbus-pinctrl"
>> + "amlogic,meson8-aobus-pinctrl"
>> + "amlogic,meson8b-aobus-pinctrl"
>
> I guess I just have to merge this. It (IIUC) turns out that the driver is beta
> and prototypeish and the DT bindings were too early to be etched in stone,
> and any old device trees using it are not really working anyways.
>
> We prefer that this not happen because we have a serious control issue
> when it comes to bindings, but sometimes it happens anyways. Like
> with divorces and other unfortunate stuff like that.
>
> Rob are you OK with this change?
Also, FYI, the driver change was merged without the corresponding DT, so
this broke booting in linux-next, so either we merge the DT/bindings
(preferred) or we revert the driver change until the DT/bindings are
sorted out.
Kevin
next prev parent reply other threads:[~2016-03-18 16:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 22:04 [PATCH 0/4] Refactor pinctrl driver for aobus / cbus Carlo Caione
2016-03-01 22:04 ` [PATCH 1/4] pinctrl: amlogic: Separate some pin functions for Meson8 / Meson8b Carlo Caione
2016-03-09 5:59 ` Linus Walleij
2016-03-01 22:04 ` [PATCH 2/4] pinctrl: amlogic: Make driver independent from two-domain configuration Carlo Caione
2016-03-09 6:01 ` Linus Walleij
2016-03-17 3:31 ` Kevin Hilman
2016-03-17 4:28 ` Kevin Hilman
2016-03-17 7:09 ` Carlo Caione
2016-03-17 15:35 ` Kevin Hilman
2016-03-17 18:15 ` Carlo Caione
2016-03-18 16:14 ` Kevin Hilman
2016-03-01 22:04 ` [PATCH 3/4] ARM: dts: amlogic: Split pinctrl device for Meson8 / Meson8b Carlo Caione
2016-03-18 17:36 ` Andreas Färber
2016-03-01 22:04 ` [PATCH 4/4] documentation: Fix pinctrl documentation " Carlo Caione
2016-03-05 4:26 ` Rob Herring
2016-03-07 9:01 ` Carlo Caione
2016-03-09 9:41 ` [PATCH v2 " Carlo Caione
2016-03-15 9:10 ` Linus Walleij
2016-03-15 9:20 ` Carlo Caione
2016-03-18 16:59 ` Kevin Hilman [this message]
2016-03-18 17:45 ` Andreas Färber
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=7h7fgzsowd.fsf@baylibre.com \
--to=khilman@baylibre$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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