[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdYK2GN_mhghhHHM+qqZ_tzy2ncu8Rm0Q7T2cagxaj7LUQ@mail.gmail.com>
Date: Thu, 17 Jan 2013 12:06:33 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Maxime Ripard <maxime.ripard@...e-electrons.com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
Grant Likely <grant.likely@...retlab.ca>,
Rob Herring <rob.herring@...xeda.com>,
Rob Landley <rob@...dley.net>,
devicetree-discuss@...ts.ozlabs.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH 1/2] ARM: sunxi: gpio: Add Allwinner SoCs GPIO drivers
On Sat, Jan 12, 2013 at 10:06 AM, Maxime Ripard
<maxime.ripard@...e-electrons.com> wrote:
>> Use gpiochip_add_pin_range() from the GPIO driver.
>>
>> An example is provided in
>> drivers/pinctrl/pinctrl-coh901.c
>
> Ok, will do. But we need to find a way to share the pins arrays between
> the pinctrl and gpio drivers then.
>
> Maybe add a pinctrl-sunxi-pins.h file? or merge the pinctrl and gpio
> drivers?
>
> I'm kind of reluctant to merging the drivers into one single messy file,
> but if that's the way to go, fine.
Well, does it have to be that messy?
You can merge it different ways.
For example there is *no* need to have two different device driver
structs and two probe functions, right?
Just one device named pinctrl that has one state container and
one single dd and probe function. That makes everything sooo
much easier I think.
Just register both a pinctrl and GPIO interface (in that order).
See the recent pinctrl-abx500.c submission for an example on
how to do this.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists