From: Gary Bisson <gary.bisson@boundarydevices.com>
To: linus.walleij@linaro.org, fabio.estevam@nxp.com
Cc: shawnguo@kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, pantelis.antoniou@konsulko.com,
vladimir_zapolskiy@mentor.com,
Gary Bisson <gary.bisson@boundarydevices.com>
Subject: [RFC v2 0/3] pinctrl: imx: add support for dt-overlays
Date: Fri, 2 Dec 2016 17:35:17 +0100 [thread overview]
Message-ID: <20161202163520.22927-1-gary.bisson@boundarydevices.com> (raw)
In-Reply-To: <20161124233824.17424-1-gary.bisson@boundarydevices.com>
Hi all,
This RFC series is a follow-up to my previous RFC patch [1].
This time the series includes one possible of_notifier implementation
for people to understand the need of radix_tree (or similar mechanism)
as suggested by Fabio.
However, if you wish to try this on, you'll need a tree with patches
from the renesas-drivers tree to have configfs support [2].
To ease that process, my testing tree was pushed to github [3] which
is based on today's linux-next tree.
Finally, the device tree overlay was also pushed to github [4]. This
last repo also contains what is needed to build the overlay out of
tree plus some helper script to load the overlay.
With this tree and overlay, two spidev devices can be added from
user-space with the proper pinctrl being applied.
The patches of this series include some comment on their purpose /
implementation.
Regards,
Gary
[1] http://www.spinics.net/lists/kernel/msg2391326.html
[2] http://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git/log/?h=topic/overlays
[3] https://github.com/gibsson/linux-next/tree/for-next-20161202
[4] https://github.com/gibsson/dt-overlays/tree/dt-overlays-next/overlays
Gary Bisson (3):
pinctrl: imx: remove const qualifier of imx_pinctrl_soc_info
pinctrl: imx: use radix trees for groups and functions
pinctrl: imx: add of_notifier for dynamic pinctrl changes
drivers/pinctrl/freescale/pinctrl-imx.c | 301 +++++++++++++++++++++++++++-----
drivers/pinctrl/freescale/pinctrl-imx.h | 5 +-
2 files changed, 261 insertions(+), 45 deletions(-)
--
2.9.3
next prev parent reply other threads:[~2016-12-02 16:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 23:38 [RFC] pinctrl: imx: use radix trees for groups and functions Gary Bisson
2016-11-30 12:48 ` Linus Walleij
2016-11-30 13:19 ` Fabio Estevam
2016-11-30 14:09 ` Gary Bisson
2016-12-02 16:35 ` Gary Bisson [this message]
2016-12-02 16:35 ` [RFC v2 1/3] pinctrl: imx: remove const qualifier of imx_pinctrl_soc_info Gary Bisson
2016-12-29 11:23 ` Fabio Estevam
2016-12-30 13:23 ` Linus Walleij
2016-12-02 16:35 ` [RFC v2 2/3] pinctrl: imx: use radix trees for groups and functions Gary Bisson
2016-12-27 13:05 ` Linus Walleij
2016-12-27 13:11 ` Fabio Estevam
2016-12-27 22:07 ` Linus Walleij
2016-12-29 9:44 ` Gary Bisson
2016-12-30 13:21 ` Linus Walleij
2016-12-30 13:25 ` Linus Walleij
2016-12-02 16:35 ` [RFC v2 3/3] pinctrl: imx: add of_notifier for dynamic pinctrl changes Gary Bisson
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=20161202163520.22927-1-gary.bisson@boundarydevices.com \
--to=gary.bisson@boundarydevices.com \
--cc=fabio.estevam@nxp.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=shawnguo@kernel.org \
--cc=vladimir_zapolskiy@mentor.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).