From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Bastian Hecht <hechtb@gmail.com>
Cc: linux-sh@vger.kernel.org, linux-input@vger.kernel.org,
Tony SIM <chinyeow.sim.xt@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [PATCH v2 2/2] ARM: shmobile: Armadillo800EVA: Move st1232 reset pin handling
Date: Mon, 08 Apr 2013 16:17:22 +0200 [thread overview]
Message-ID: <1534841.hHClRQAXMk@avalon> (raw)
In-Reply-To: <1365425547-10391-2-git-send-email-hechtb+renesas@gmail.com>
Hi Bastian,
Thanks for the patch.
On Monday 08 April 2013 14:52:27 Bastian Hecht wrote:
> We no longer need to set up the reset pin for the st1232 in the board
> code, but can pass the GPIO number via the platform data to the driver.
> This results in a cleaner grouping of the device setup.
>
> Signed-off-by: Bastian Hecht <hechtb+renesas@gmail.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
> v2:
> reset_pin changed to reset_gpio
>
> arch/arm/mach-shmobile/board-armadillo800eva.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-shmobile/board-armadillo800eva.c
> b/arch/arm/mach-shmobile/board-armadillo800eva.c index bf4c3d2..d1c1ff4
> 100644
> --- a/arch/arm/mach-shmobile/board-armadillo800eva.c
> +++ b/arch/arm/mach-shmobile/board-armadillo800eva.c
> @@ -24,6 +24,7 @@
> #include <linux/err.h>
> #include <linux/kernel.h>
> #include <linux/input.h>
> +#include <linux/input/st1232_pdata.h>
> #include <linux/irq.h>
> #include <linux/platform_device.h>
> #include <linux/gpio.h>
> @@ -997,10 +998,15 @@ static struct platform_device i2c_gpio_device = {
> };
>
> /* I2C */
> +static struct st1232_pdata st1232_i2c0_pdata = {
> + .reset_gpio = 166,
> +};
> +
> static struct i2c_board_info i2c0_devices[] = {
> {
> I2C_BOARD_INFO("st1232-ts", 0x55),
> .irq = irq_pin(10),
> + .platform_data = &st1232_i2c0_pdata,
> },
> {
> I2C_BOARD_INFO("wm8978", 0x1a),
> @@ -1120,7 +1126,6 @@ static void __init eva_init(void)
>
> /* Touchscreen */
> gpio_request(GPIO_FN_IRQ10, NULL); /* TP_INT */
> - gpio_request_one(166, GPIOF_OUT_INIT_HIGH, NULL); /* TP_RST_B */
>
> /* GETHER */
> gpio_request(GPIO_FN_ET_CRS, NULL);
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-04-08 14:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 12:52 [PATCH v2 1/2] input: st1232: Add reset pin handling Bastian Hecht
2013-04-08 12:52 ` [PATCH v2 2/2] ARM: shmobile: Armadillo800EVA: Move st1232 " Bastian Hecht
2013-04-08 14:17 ` Laurent Pinchart [this message]
2013-04-09 8:26 ` Simon Horman
2013-04-09 9:11 ` Simon Horman
2013-04-09 9:16 ` Bastian Hecht
2013-04-09 11:55 ` Simon Horman
2013-04-09 15:01 ` Simon Horman
2013-04-09 15:04 ` Bastian Hecht
2013-04-08 14:17 ` [PATCH v2 1/2] input: st1232: Add " Laurent Pinchart
2013-04-09 8:28 ` Simon Horman
2013-04-09 9:23 ` Bastian Hecht
2013-04-09 15:01 ` Simon Horman
2013-04-10 6:51 ` Dmitry Torokhov
2013-04-10 7:25 ` Simon Horman
2013-04-10 6:51 ` Dmitry Torokhov
2013-04-10 9:11 ` Laurent Pinchart
2013-04-10 21:38 ` Bastian Hecht
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=1534841.hHClRQAXMk@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=chinyeow.sim.xt@renesas.com \
--cc=hechtb@gmail.com \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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).