From: Dmitry Torokhov <dtor@insightbb.com>
To: eric miao <eric.y.miao@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH 2/12] pxa: remove the pin configuration from the keypad driver
Date: Tue, 29 Jan 2008 02:21:26 -0500 [thread overview]
Message-ID: <200801290221.26877.dtor@insightbb.com> (raw)
In-Reply-To: <f17812d70801282251g79b7c29ehf1f6afdf5274fcd4@mail.gmail.com>
On Tuesday 29 January 2008 01:51, eric miao wrote:
> On Jan 29, 2008 2:24 PM, Dmitry Torokhov <dtor@insightbb.com> wrote:
> > Hi Eric,
> >
> > On Wednesday 23 January 2008 02:17, eric miao wrote:
> > > From dbd62bced0f789765d1823f66af792933c6b46a1 Mon Sep 17 00:00:00 2001
> > > From: eric miao <eric.miao@marvell.com>
> > > Date: Tue, 22 Jan 2008 16:34:12 +0800
> > > Subject: [PATCH] pxa: remove the pin configuration from the keypad driver
> > >
> > > The pin configurations will slowly be moved to the board specific code
> > > at initialization thus to make the driver more generic.
> > >
> > > Signed-off-by: eric miao <eric.miao@marvell.com>
> > > ---
> > > drivers/input/keyboard/pxa27x_keypad.c | 4 ----
> > > include/asm-arm/arch-pxa/pxa27x_keypad.h | 1 -
> > > 2 files changed, 0 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/drivers/input/keyboard/pxa27x_keypad.c
> > > b/drivers/input/keyboard/pxa27x_keypad.c
> > > index 06c1d5a..43fb63d 100644
> > > --- a/drivers/input/keyboard/pxa27x_keypad.c
> > > +++ b/drivers/input/keyboard/pxa27x_keypad.c
> > > @@ -208,10 +208,6 @@ static int __devinit pxa27x_keypad_probe(struct
> > > platform_device *pdev)
> > > if (error)
> > > goto err_free_irq;
> > >
> > > - /* Setup GPIOs. */
> > > - for (i = 0; i < pdata->nr_rows + pdata->nr_cols; i++)
> > > - pxa_gpio_mode(pdata->gpio_modes[i]);
> > > -
> >
> > That would require GPIO code to be replicated in every subarch piece. Do you
> > expect many boards require special GPIO setup or maybe it would make sense
> > to keep something similar to the code above (possibly have pointer to array
> > of gpio modes and array size in pdata)? This way simpler boards will just
> > supply the list and more complex setups can still do it themselves?
> >
>
> Actually, pin configurations on different platforms vary much, and to keep
> the driver generic enough, this stuff should really be pushed to the platform
> code.
>
> Currently, we (Nicolas, Russell King and I) are proposing a similar
> pin configuration scheme as pxa3xx is currently doing for pxa{25x,27x}.
>
> The specific reasons behind this change are:
>
> 1. pxa3xx uses a different mechanism and API to configure pins other
> than the pxa{25x,27x}'s pxa_gpio_mode(), i.e., pxa_gpio_mode() is
> no longer valid for pxa3xx. So this is really processor specific code
> we need to keep out side of the driver
Ok, fair enough.
--
Dmitry
next prev parent reply other threads:[~2008-01-29 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 7:17 [PATCH 2/12] pxa: remove the pin configuration from the keypad driver eric miao
2008-01-29 6:24 ` Dmitry Torokhov
2008-01-29 6:51 ` eric miao
2008-01-29 7:21 ` Dmitry Torokhov [this message]
2008-01-29 11:54 ` Dmitry Baryshkov
2008-01-30 0:13 ` eric miao
2008-01-30 0:52 ` Dmitry Baryshkov
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=200801290221.26877.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=eric.y.miao@gmail.com \
--cc=linux-input@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: 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).