From: Shawn Guo <shawn.guo@linaro.org> To: linux-kernel@vger.kernel.org Cc: grant.likely@secretlab.ca, linus.walleij@linaro.org, kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org, patches@linaro.org Subject: [PATCH 0/4] add gpio driver gpio-mxs Date: Fri, 20 May 2011 17:51:25 +0800 [thread overview] Message-ID: <1305885089-27343-1-git-send-email-shawn.guo@linaro.org> (raw) The patch set is to move Freescale MXS gpio driver from mach-mxs into drivers/gpio. Different from u300 gpio driver that all gpio ports are registered as one device, gpio-mxs expects every single port is a gpio device. The first 3 patches are just to ease review and can be squashed into the last one. Shawn Guo (4): gpio: gpio-mxs: add file gpio-mxs.c gpio: gpio-mxs: drop mach-specific accessors gpio: gpio-mxs: remove gpio port definition and registration gpio: gpio-mxs: add gpio driver for Freescale MXS architecture drivers/gpio/Kconfig | 3 + drivers/gpio/Makefile | 1 + drivers/gpio/gpio-mxs.c | 371 +++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 375 insertions(+), 0 deletions(-) Regards, Shawn
WARNING: multiple messages have this Message-ID (diff)
From: shawn.guo@linaro.org (Shawn Guo) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/4] add gpio driver gpio-mxs Date: Fri, 20 May 2011 17:51:25 +0800 [thread overview] Message-ID: <1305885089-27343-1-git-send-email-shawn.guo@linaro.org> (raw) The patch set is to move Freescale MXS gpio driver from mach-mxs into drivers/gpio. Different from u300 gpio driver that all gpio ports are registered as one device, gpio-mxs expects every single port is a gpio device. The first 3 patches are just to ease review and can be squashed into the last one. Shawn Guo (4): gpio: gpio-mxs: add file gpio-mxs.c gpio: gpio-mxs: drop mach-specific accessors gpio: gpio-mxs: remove gpio port definition and registration gpio: gpio-mxs: add gpio driver for Freescale MXS architecture drivers/gpio/Kconfig | 3 + drivers/gpio/Makefile | 1 + drivers/gpio/gpio-mxs.c | 371 +++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 375 insertions(+), 0 deletions(-) Regards, Shawn
next reply other threads:[~2011-05-20 9:44 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-20 9:51 Shawn Guo [this message] 2011-05-20 9:51 ` [PATCH 0/4] add gpio driver gpio-mxs Shawn Guo 2011-05-20 9:51 ` [PATCH 1/4] gpio: gpio-mxs: add file gpio-mxs.c Shawn Guo 2011-05-20 9:51 ` Shawn Guo 2011-05-20 9:51 ` [PATCH 2/4] gpio: gpio-mxs: drop mach-specific accessors Shawn Guo 2011-05-20 9:51 ` Shawn Guo 2011-05-20 9:51 ` [PATCH 3/4] gpio: gpio-mxs: remove gpio port definition and registration Shawn Guo 2011-05-20 9:51 ` Shawn Guo 2011-05-20 9:51 ` [PATCH 4/4] gpio: gpio-mxs: add gpio driver for Freescale MXS architecture Shawn Guo 2011-05-20 9:51 ` Shawn Guo 2011-05-20 11:24 ` Sascha Hauer 2011-05-20 11:24 ` Sascha Hauer 2011-05-20 14:31 ` Shawn Guo 2011-05-20 14:31 ` Shawn Guo 2011-05-20 10:02 ` [PATCH 0/4] add gpio driver gpio-mxs Sascha Hauer 2011-05-20 10:02 ` Sascha Hauer 2011-05-20 10:24 ` Shawn Guo 2011-05-20 11:25 ` Sascha Hauer 2011-05-20 11:25 ` Sascha Hauer 2011-05-27 3:15 ` Grant Likely 2011-05-27 3:15 ` Grant Likely
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=1305885089-27343-1-git-send-email-shawn.guo@linaro.org \ --to=shawn.guo@linaro.org \ --cc=grant.likely@secretlab.ca \ --cc=kernel@pengutronix.de \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=patches@linaro.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.