From: Rajendra Nayak <rnayak@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linus.walleij@stericsson.com, linux-omap@vger.kernel.org,
linaro-dev@lists.linaro.org
Subject: Re: [RFC 1/3] pinctrl: add a driver for the OMAP pinmux
Date: Tue, 15 Nov 2011 10:03:33 +0530 [thread overview]
Message-ID: <4EC1EB9D.1000503@ti.com> (raw)
In-Reply-To: <20111114172312.GI31337@atomide.com>
On Monday 14 November 2011 10:53 PM, Tony Lindgren wrote:
> * Rajendra Nayak<rnayak@ti.com> [111114 04:05]:
>> > --- /dev/null
>> > +++ b/drivers/pinctrl/pinmux-omap.c
>> > @@ -0,0 +1,735 @@
>> > +
>> > +/* omap4 core pads */
>> > +static const struct pinctrl_pin_desc omap4_core_pads[] = {
>> > + PINCTRL_PIN(0, "c12"),
>> > + PINCTRL_PIN(1, "d12"),
>> > + PINCTRL_PIN(2, "c13"),
> ...
>
> Let's not even plan on adding this data here. We already have
> about 6000 lines of pinmux data for omaps even without this patch.
>
> Instead, just write something as a separate patch that populates
> omap pinmux data from the existing data until we have the data
> coming from DT.
>
But the plan is to get rid of those 6000 lines of pinmux data that
exists today for OMAP. I did not remove it now, because I still need
to take care of the pull up/down configurations which are missing.
Once thats in place, we can get rid of the existing data completely.
Linus,
Is there a plan to move even the data that exists in the pinmux
drivers today (including the function/pin-groups definition)
eventually to DT? Or is it just the 'mapping' data to map
devices to functions (that today is done from board files) which
alone will be moved?
regards,
Rajendra
next prev parent reply other threads:[~2011-11-15 4:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 12:40 [RFC 0/3] OMAP pinmux driver Rajendra Nayak
2011-11-14 12:40 ` [RFC 1/3] pinctrl: add a driver for the OMAP pinmux Rajendra Nayak
2011-11-14 17:23 ` Tony Lindgren
2011-11-15 4:33 ` Rajendra Nayak [this message]
2011-11-17 8:08 ` Linus Walleij
2011-11-17 11:26 ` Thomas Abraham
2011-11-17 13:57 ` Linus Walleij
[not found] ` <CACRpkdbBQoOU8hyew6tXth3Ohrg5_rN7M+tbVsYFcOjgq73aCw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-22 11:09 ` Thomas Abraham
2011-11-22 12:05 ` Linus Walleij
2011-11-22 17:54 ` Tony Lindgren
2011-11-23 0:28 ` Stephen Warren
2011-11-23 10:14 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF174F08C5B3-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-11-24 10:09 ` Linus Walleij
2011-11-23 15:21 ` Koen Kooi
2011-11-24 5:07 ` Hiremath, Vaibhav
2011-11-24 10:04 ` Linus Walleij
2011-11-24 19:54 ` Tony Lindgren
2011-11-25 8:53 ` Linus Walleij
2011-11-17 8:20 ` Linus Walleij
2011-11-17 10:50 ` Rajendra Nayak
2011-11-14 12:40 ` [RFC 2/3] ARM: omap4: Add omap4 pinmux devices for core and wkup Rajendra Nayak
2011-11-14 12:40 ` [RFC 3/3] ARM: omap4: Add pinmux map in SDP and PANDA board files Rajendra Nayak
2011-11-17 8:22 ` [RFC 0/3] OMAP pinmux driver Linus Walleij
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=4EC1EB9D.1000503@ti.com \
--to=rnayak@ti.com \
--cc=linaro-dev@lists.linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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