From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
linus.walleij@linaro.org
Cc: Ludovic Desroches <ludovic.desroches@atmel.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] get pinctrl more flexible for per pin muxing controllers
Date: Wed, 3 Jun 2015 15:31:56 +0200 [thread overview]
Message-ID: <556F01CC.8020305@atmel.com> (raw)
In-Reply-To: <1430729776-27797-1-git-send-email-ludovic.desroches@atmel.com>
Le 04/05/2015 10:56, Ludovic Desroches a écrit :
> Hi,
>
> The way pins, groups and functions are tied is too constraining for some
> controllers. It concerns mainly the ones we don't care about groups and
> functions, each pin can be muxed to any functions.
> The goal of these two patches is too remove some of the constraints.
>
> I have added the prototype of a pin controller and device tree to show the
> way I want to use these changes. I couldn't test it on boards using generic
> pinconf so I am not sure that I don't break something...
>
>
> Ludovic Desroches (4):
> pinctrl: change function behavior for per pin muxing controllers
> pinctrl: introduce complex pin description
Linus,
Ludovic sent this series nearly one month ago. It was posted after a RFC
series on the same topic two months ago. As we don't see any comment on
neither of them we assume that it's okay to include them.
So, is it possible for you to merge these 2 patches in
pinmux/pinconf-generic? The driver making use of this work, which was
marked a "PROTO" in the series sent by Ludovic, is being finalized and
sent: it would be good to have it working early.
Best regards,
> pinctrl: rough draft for a future controller
> ARM: at91/dt: proto dt
>
> arch/arm/boot/dts/Makefile | 1 +
> arch/arm/boot/dts/at91-sama5d4ek_proto.dts | 243 ++++++++++
> arch/arm/boot/dts/sama5d4_proto-pinfunc.h | 463 +++++++++++++++++++
> arch/arm/boot/dts/sama5d4_proto.dtsi | 716 +++++++++++++++++++++++++++++
> drivers/pinctrl/Kconfig | 10 +
> drivers/pinctrl/Makefile | 1 +
> drivers/pinctrl/pinconf-generic.c | 44 +-
> drivers/pinctrl/pinctrl-at91-pio4.c | 625 +++++++++++++++++++++++++
> drivers/pinctrl/pinmux.c | 58 +--
> include/linux/pinctrl/pinctrl.h | 6 +
> include/linux/pinctrl/pinmux.h | 3 +
> 11 files changed, 2134 insertions(+), 36 deletions(-)
> create mode 100644 arch/arm/boot/dts/at91-sama5d4ek_proto.dts
> create mode 100644 arch/arm/boot/dts/sama5d4_proto-pinfunc.h
> create mode 100644 arch/arm/boot/dts/sama5d4_proto.dtsi
> create mode 100644 drivers/pinctrl/pinctrl-at91-pio4.c
>
--
Nicolas Ferre
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-06-03 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 8:56 [PATCH 0/2] get pinctrl more flexible for per pin muxing controllers Ludovic Desroches
2015-05-04 8:56 ` [PATCH 1/2] pinctrl: change function behavior " Ludovic Desroches
[not found] ` <1430729776-27797-1-git-send-email-ludovic.desroches-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2015-05-04 8:56 ` [PATCH 2/2] pinctrl: introduce complex pin description Ludovic Desroches
2015-05-04 8:56 ` [PROTO] pinctrl: rough draft for a future controller Ludovic Desroches
2015-05-04 8:56 ` [PROTO] ARM: at91/dt: proto dt Ludovic Desroches
2015-06-03 13:31 ` Nicolas Ferre [this message]
[not found] ` <556F01CC.8020305-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2015-06-10 7:33 ` [PATCH 0/2] get pinctrl more flexible for per pin muxing controllers Linus Walleij
2015-06-10 14:14 ` Stephen Warren
2015-06-10 15:00 ` Ludovic Desroches
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=556F01CC.8020305@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
/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).