All of lore.kernel.org
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] pinctrl: common handling of generic pinconfig props in dt
Date: Mon, 10 Jun 2013 21:39:32 +0200	[thread overview]
Message-ID: <201306102139.32444.heiko@sntech.de> (raw)

Hi Linus,

here is my second try ... after our talk today, hopefully more future proof
(and acceptable).

I hadn't found a way to have the phandle as a simple argument in the pins
property, so the example Rockchip driver now uses a second property
rockchip,config = <&phandle>; to hold the link to the config node.

Surprisingly everything still works ;-) .


Heiko Stuebner (2):
  pinctrl: add function to parse generic pinconfig properties from a dt node
  pinctrl: add pinctrl driver for Rockchip SoCs

 .../bindings/pinctrl/pinctrl-bindings.txt          |   38 +
 .../bindings/pinctrl/rockchip,pinctrl.txt          |   98 ++
 drivers/pinctrl/Kconfig                            |    6 +
 drivers/pinctrl/Makefile                           |    1 +
 drivers/pinctrl/pinconf-generic.c                  |   81 ++
 drivers/pinctrl/pinconf.h                          |    6 +
 drivers/pinctrl/pinctrl-rockchip.c                 | 1346 ++++++++++++++++++++
 include/dt-bindings/pinctrl/rockchip.h             |   32 +
 8 files changed, 1608 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.txt
 create mode 100644 drivers/pinctrl/pinctrl-rockchip.c
 create mode 100644 include/dt-bindings/pinctrl/rockchip.h

-- 
1.7.2.3

WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Patrice Chotard <patrice.chotard.st@gmail.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/2] pinctrl: common handling of generic pinconfig props in dt
Date: Mon, 10 Jun 2013 21:39:32 +0200	[thread overview]
Message-ID: <201306102139.32444.heiko@sntech.de> (raw)

Hi Linus,

here is my second try ... after our talk today, hopefully more future proof
(and acceptable).

I hadn't found a way to have the phandle as a simple argument in the pins
property, so the example Rockchip driver now uses a second property
rockchip,config = <&phandle>; to hold the link to the config node.

Surprisingly everything still works ;-) .


Heiko Stuebner (2):
  pinctrl: add function to parse generic pinconfig properties from a dt node
  pinctrl: add pinctrl driver for Rockchip SoCs

 .../bindings/pinctrl/pinctrl-bindings.txt          |   38 +
 .../bindings/pinctrl/rockchip,pinctrl.txt          |   98 ++
 drivers/pinctrl/Kconfig                            |    6 +
 drivers/pinctrl/Makefile                           |    1 +
 drivers/pinctrl/pinconf-generic.c                  |   81 ++
 drivers/pinctrl/pinconf.h                          |    6 +
 drivers/pinctrl/pinctrl-rockchip.c                 | 1346 ++++++++++++++++++++
 include/dt-bindings/pinctrl/rockchip.h             |   32 +
 8 files changed, 1608 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.txt
 create mode 100644 drivers/pinctrl/pinctrl-rockchip.c
 create mode 100644 include/dt-bindings/pinctrl/rockchip.h

-- 
1.7.2.3


             reply	other threads:[~2013-06-10 19:39 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 19:39 Heiko Stübner [this message]
2013-06-10 19:39 ` [PATCH v2 0/2] pinctrl: common handling of generic pinconfig props in dt Heiko Stübner
2013-06-10 19:40 ` [PATCH 1/2] pinctrl: add function to parse generic pinconfig properties from a dt node Heiko Stübner
2013-06-10 19:40   ` Heiko Stübner
2013-06-11  8:48   ` Linus Walleij
2013-06-11  8:48     ` Linus Walleij
2013-06-12 14:55   ` James Hogan
2013-06-12 14:55     ` James Hogan
2013-06-12 22:22     ` Heiko Stübner
2013-06-12 22:22       ` Heiko Stübner
2013-06-13  8:11       ` Linus Walleij
2013-06-13  8:11         ` Linus Walleij
2013-06-13 14:35         ` Heiko Stübner
2013-06-13 14:35           ` Heiko Stübner
2013-06-13 15:23           ` Heiko Stübner
2013-06-13 15:23             ` Heiko Stübner
2013-06-13 15:36             ` Linus Walleij
2013-06-13 15:36               ` Linus Walleij
2013-06-13 23:53               ` Laurent Pinchart
2013-06-13 23:53                 ` Laurent Pinchart
2013-06-14  9:18                 ` Heiko Stübner
2013-06-14  9:18                   ` Heiko Stübner
2013-06-14 14:52                   ` Laurent Pinchart
2013-06-14 14:52                     ` Laurent Pinchart
2013-06-16 10:39                     ` Linus Walleij
2013-06-16 10:39                       ` Linus Walleij
2013-06-13 15:31           ` Linus Walleij
2013-06-13 15:31             ` Linus Walleij
2013-06-14  0:27   ` Laurent Pinchart
2013-06-14  0:27     ` Laurent Pinchart
2013-06-14  7:34     ` Heiko Stübner
2013-06-14  7:34       ` Heiko Stübner
2013-06-14 14:46       ` Laurent Pinchart
2013-06-14 14:46         ` Laurent Pinchart
2013-06-10 19:42 ` [PATCH 2/2] pinctrl: add pinctrl driver for Rockchip SoCs Heiko Stübner
2013-06-10 19:42   ` Heiko Stübner
2013-06-10 20:16   ` [PATCH 2/2 v3] " Heiko Stübner
2013-06-10 20:16     ` Heiko Stübner
2013-06-11  8:53     ` Linus Walleij
2013-06-11  8:53       ` Linus Walleij

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=201306102139.32444.heiko@sntech.de \
    --to=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.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.