From: Tony Prisk <linux@prisktech.co.nz> To: linux-arm-kernel@lists.infradead.org Cc: linux-kernel@vger.kernel.org, grant.likely@secretlab.ca, linus.walleij@linaro.org, Tony Prisk <linux@prisktech.co.nz> Subject: [RFC PATCH] Add pin control driver for Wondermedia SoCS Date: Fri, 15 Feb 2013 15:48:53 +1300 [thread overview] Message-ID: <1360896534-20637-1-git-send-email-linux@prisktech.co.nz> (raw) Before I get all carried away and start filling in all the data for this driver, I was hoping someone (or a few people) could review the basic design in case it requires changes to the data structures. This driver is based on pinctrl-bcm2835.c as it seems to be similar in design. The pin controller on Wondermedia SoC's only allows each pin to either be a GPIO or to be its 'alternate' function. Functions cannot be remapped to any other pin. I have seperated out the data from the code as there are several SoC's to support and each has it's own variation of registers / pin layout. I borrowed this part of the design from the Tegra pinctrl driver. Regards Tony Prisk Tony Prisk (1): pinctrl: gpio: vt8500: Add pin control driver for Wondermedia SoCs arch/arm/Kconfig | 4 +- arch/arm/boot/dts/wm8850-w70v2.dts | 15 + arch/arm/boot/dts/wm8850.dtsi | 7 +- arch/arm/mach-vt8500/Kconfig | 1 + drivers/pinctrl/Kconfig | 10 + drivers/pinctrl/Makefile | 2 + drivers/pinctrl/pinctrl-wm8850.c | 166 +++++++++++ drivers/pinctrl/pinctrl-wmt.c | 565 ++++++++++++++++++++++++++++++++++++ drivers/pinctrl/pinctrl-wmt.h | 73 +++++ 9 files changed, 840 insertions(+), 3 deletions(-) create mode 100644 drivers/pinctrl/pinctrl-wm8850.c create mode 100644 drivers/pinctrl/pinctrl-wmt.c create mode 100644 drivers/pinctrl/pinctrl-wmt.h -- 1.7.9.5
WARNING: multiple messages have this Message-ID (diff)
From: linux@prisktech.co.nz (Tony Prisk) To: linux-arm-kernel@lists.infradead.org Subject: [RFC PATCH] Add pin control driver for Wondermedia SoCS Date: Fri, 15 Feb 2013 15:48:53 +1300 [thread overview] Message-ID: <1360896534-20637-1-git-send-email-linux@prisktech.co.nz> (raw) Before I get all carried away and start filling in all the data for this driver, I was hoping someone (or a few people) could review the basic design in case it requires changes to the data structures. This driver is based on pinctrl-bcm2835.c as it seems to be similar in design. The pin controller on Wondermedia SoC's only allows each pin to either be a GPIO or to be its 'alternate' function. Functions cannot be remapped to any other pin. I have seperated out the data from the code as there are several SoC's to support and each has it's own variation of registers / pin layout. I borrowed this part of the design from the Tegra pinctrl driver. Regards Tony Prisk Tony Prisk (1): pinctrl: gpio: vt8500: Add pin control driver for Wondermedia SoCs arch/arm/Kconfig | 4 +- arch/arm/boot/dts/wm8850-w70v2.dts | 15 + arch/arm/boot/dts/wm8850.dtsi | 7 +- arch/arm/mach-vt8500/Kconfig | 1 + drivers/pinctrl/Kconfig | 10 + drivers/pinctrl/Makefile | 2 + drivers/pinctrl/pinctrl-wm8850.c | 166 +++++++++++ drivers/pinctrl/pinctrl-wmt.c | 565 ++++++++++++++++++++++++++++++++++++ drivers/pinctrl/pinctrl-wmt.h | 73 +++++ 9 files changed, 840 insertions(+), 3 deletions(-) create mode 100644 drivers/pinctrl/pinctrl-wm8850.c create mode 100644 drivers/pinctrl/pinctrl-wmt.c create mode 100644 drivers/pinctrl/pinctrl-wmt.h -- 1.7.9.5
next reply other threads:[~2013-02-15 2:48 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-15 2:48 Tony Prisk [this message] 2013-02-15 2:48 ` [RFC PATCH] Add pin control driver for Wondermedia SoCS Tony Prisk 2013-02-15 2:48 ` [PATCH] pinctrl: gpio: vt8500: Add pin control driver for Wondermedia SoCs Tony Prisk 2013-02-15 2:48 ` Tony Prisk 2013-02-15 20:27 ` Linus Walleij 2013-02-15 20:27 ` Linus Walleij 2013-02-15 22:26 ` Tony Prisk 2013-02-15 22:26 ` Tony Prisk 2013-02-27 22:21 ` Stephen Warren 2013-02-27 22:21 ` Stephen Warren 2013-02-28 6:25 ` Tony Prisk 2013-02-28 6:25 ` Tony Prisk 2013-03-01 18:24 ` Stephen Warren 2013-03-01 18:24 ` Stephen Warren
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=1360896534-20637-1-git-send-email-linux@prisktech.co.nz \ --to=linux@prisktech.co.nz \ --cc=grant.likely@secretlab.ca \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.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: linkBe 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.