From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: omap2plus: fix ads7846 pendown gpio request
Date: Tue, 31 May 2011 04:12:46 -0700 [thread overview]
Message-ID: <20110531111246.GX11352@atomide.com> (raw)
In-Reply-To: <4DDE5C8B.7030308@compulab.co.il>
* Igor Grinberg <grinberg@compulab.co.il> [110526 06:54]:
> ping
>
> On 05/11/11 10:35, Igor Grinberg wrote:
>
> > Tony,
> >
> >
> > You can fold this one to the original patch from Mike as well,
> >
> > or do you want it into the rc1?
Thanks adding to fixes.
Tony
> >
> >
> >
> > On 05/04/11 20:22, Thomas Weber wrote:
> >
> >> Am 04.05.2011 17:04, schrieb Igor Grinberg:
> >>> introduced by: 96974a24
> >>> (omap: consolidate touch screen initialization among different boards)
> >>>
> >>> ads7846 driver can use either gpio_pendown or get_pendown_state()
> >>> callback. In case of gpio_pendown, it requests the provided gpio_pendown
> >>> thus resulting in double requesting that gpio:
> >>>
> >>> ads7846 spi1.0: failed to request pendown GPIO57
> >>> ads7846: probe of spi1.0 failed with error -16
> >>>
> >>> Fix this by restricting the gpio request to the case of
> >>> get_pendown_state() callback is used.
> >>>
> >>> Signed-off-by: Igor Grinberg<grinberg@compulab.co.il>
> >>> ---
> >>> arch/arm/mach-omap2/common-board-devices.c | 20 ++++++++++----------
> >>> 1 files changed, 10 insertions(+), 10 deletions(-)
> >>>
> >>> diff --git a/arch/arm/mach-omap2/common-board-devices.c b/arch/arm/mach-omap2/common-board-devices.c
> >>> index d57c71d..61fee80 100644
> >>> --- a/arch/arm/mach-omap2/common-board-devices.c
> >>> +++ b/arch/arm/mach-omap2/common-board-devices.c
> >>> @@ -83,17 +83,17 @@ void __init omap_ads7846_init(int bus_num, int gpio_pendown, int gpio_debounce,
> >>> struct spi_board_info *spi_bi =&ads7846_spi_board_info;
> >>> int err;
> >>>
> >>> - err = gpio_request(gpio_pendown, "TS PenDown");
> >>> - if (err) {
> >>> - pr_err("Could not obtain gpio for TS PenDown: %d\n", err);
> >>> - return;
> >>> - }
> >>> -
> >>> - gpio_direction_input(gpio_pendown);
> >>> - gpio_export(gpio_pendown, 0);
> >>> + if (board_pdata&& board_pdata->get_pendown_state) {
> >>> + err = gpio_request_one(gpio_pendown, GPIOF_IN, "TSPenDown");
> >>> + if (err) {
> >>> + pr_err("Couldn't obtain gpio for TSPenDown: %d\n", err);
> >>> + return;
> >>> + }
> >>> + gpio_export(gpio_pendown, 0);
> >>>
> >>> - if (gpio_debounce)
> >>> - gpio_set_debounce(gpio_pendown, gpio_debounce);
> >>> + if (gpio_debounce)
> >>> + gpio_set_debounce(gpio_pendown, gpio_debounce);
> >>> + }
> >>>
> >>> ads7846_config.gpio_pendown = gpio_pendown;
> >>>
> >> Tested-by: Thomas Weber <weber@corscience.de>
> >>
> >> On Devkit8000.
> >>
>
> --
> Regards,
> Igor.
>
prev parent reply other threads:[~2011-05-31 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 15:04 [PATCH] arm: omap2plus: fix ads7846 pendown gpio request Igor Grinberg
2011-05-04 17:22 ` Thomas Weber
2011-05-11 7:35 ` Igor Grinberg
2011-05-26 13:58 ` Igor Grinberg
2011-05-31 11:12 ` Tony Lindgren [this message]
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=20110531111246.GX11352@atomide.com \
--to=tony@atomide.com \
--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 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).