From: Linus Walleij <linus.walleij@linaro.org>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Stephen Warren <swarren@wwwdotorg.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"arm@kernel.org" <arm@kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: dt: at91: new binding
Date: Tue, 17 Mar 2015 13:07:19 +0100 [thread overview]
Message-ID: <CACRpkdbNLE+VjhvSgsU4oqAc03ieCNyiLkUzbjEiu_LFof-Unw@mail.gmail.com> (raw)
In-Reply-To: <1424943294-8805-1-git-send-email-plagnioj@jcrosoft.com>
On Thu, Feb 26, 2015 at 10:34 AM, Jean-Christophe PLAGNIOL-VILLARD
<plagnioj@jcrosoft.com> wrote:
> +For each peripheral/bank we will descibe in a u32 if a pin can be
> +configured in it by putting 1 to the pin bit (1 << pin)
This seems to be describing driver intrinsics in the device tree, like
how the hardware is routed on the inside and what it can do.
IMO that is driver territory, the driver should know these limitations
and protest if you try to do something illegal.
Anyway as the AT91 maintainers seem to disagree I will allow some
more time for discussion before merging the patch.
I can't really have one AT91 maintainer NACKing another, it doesn't
matter that this is a separate driver, in my book the MAINTAINERS
entry for AT91 as a whole overrides that so can you please find an
agreement on how to handle this or I will stall the patch until
you're in agreement.
ARM SoC maintainers input would be welcomed.
Yours,
Linus Walleij
next prev parent reply other threads:[~2015-03-17 12:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 9:34 [PATCH] pinctrl: dt: at91: new binding Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <1424943294-8805-1-git-send-email-plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
2015-02-26 10:43 ` Ludovic Desroches
2015-02-26 11:03 ` Jean-Christophe PLAGNIOL-VILLARD
2015-03-06 15:08 ` Nicolas Ferre
2015-03-06 16:49 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <AB034DC5-9E4C-4883-BBF0-B93B438C7A54-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
2015-03-06 17:07 ` Alexandre Belloni
2015-03-06 18:23 ` Boris Brezillon
2015-03-06 18:33 ` Jean-Christophe PLAGNIOL-VILLARD
2015-03-17 12:07 ` Linus Walleij [this message]
2015-03-29 20:55 ` Olof Johansson
2015-04-02 8:18 ` Jean-Christophe PLAGNIOL-VILLARD
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=CACRpkdbNLE+VjhvSgsU4oqAc03ieCNyiLkUzbjEiu_LFof-Unw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=arm@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).