From: Linus Walleij <linus.walleij@linaro.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Chen-Yu Tsai <wens@csie.org>
Subject: Re: Requesting as a GPIO a pin already used through pinctrl
Date: Sun, 6 Nov 2016 11:11:30 +0100 [thread overview]
Message-ID: <CACRpkdbwCMWum8Co91DnL0GgOvihud1M3HnPZTdRvKoj_RRWbA@mail.gmail.com> (raw)
In-Reply-To: <20161102213142.ajano4g4oizusv74@lukather>
On Wed, Nov 2, 2016 at 10:31 PM, Maxime Ripard
<maxime.ripard@free-electrons.com> wrote:
> So no, I really don't think the DT ABI matters here, or at least
> compared to the bug we face and the changes that we would need to make
> in order to fix it. But Mark will probably disagree.
In this case we have to think about that it is a community effort driving
DT standardization for the community, the company Allwinner is not
actively involved.
I think etching DT bindings in stone is for companies shipping products.
Those decisions will affect their internal company culture and therefore
we exercise pressure on them as a standards body. It is a clear message
that they need to work together to standardize and take responsibility for
what they ship.
For community efforts just wanting to have a nice and upstream-compliant
structure on things, the requirements for ABI should be lower. Getting the
community code to even run on the device is a hacker undertaking already
in the first place, and the community is using their precious free time for
this.
Yours,
Linus Walleij
prev parent reply other threads:[~2016-11-06 10:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 13:58 Requesting as a GPIO a pin already used through pinctrl Maxime Ripard
2016-09-18 11:30 ` Linus Walleij
2016-09-21 19:51 ` Maxime Ripard
2016-09-21 20:34 ` Michael Welling
2016-09-22 10:48 ` Maxime Ripard
2016-09-22 15:46 ` Michael Welling
2016-09-23 13:22 ` Linus Walleij
2016-09-23 15:24 ` Vladimir Zapolskiy
2016-09-23 21:34 ` Maxime Ripard
2016-09-30 16:26 ` Linus Walleij
2016-09-23 21:05 ` Maxime Ripard
2016-10-26 15:49 ` Maxime Ripard
2016-10-27 12:12 ` Linus Walleij
2016-11-02 21:31 ` Maxime Ripard
2016-11-06 10:11 ` Linus Walleij [this message]
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=CACRpkdbwCMWum8Co91DnL0GgOvihud1M3HnPZTdRvKoj_RRWbA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=gnurou@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=nicolas.ferre@atmel.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=wens@csie.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 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.