On Tue, Nov 15, 2011 at 5:33 AM, Rajendra Nayak <rna...@ti.com> wrote:
> On Monday 14 November 2011 10:53 PM, Tony Lindgren wrote:
>> * Rajendra Nayak<rna...@ti.com> [111114 04:05]:
>>>
>>> > +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.
>>
> 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?
Not for the U300 driver, for the simple reason that it cannot
use device tree. So both methods of providing the data need
to be allowed - either as static data (the U300 driver does not
even have platform data, the pin data is encoded in the driver
itself since it's tied to U300 and not used for any other systems
or variants) or as device tree lookups.
That said I have no clue on how to make the DT bindings
FTM, patches and suggestions welcome.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
