* Tony Lindgren t...@atomide.com [100924 17:14]:
* Benoit Cousson b-cous...@ti.com [100924 02:07]:
If we wanted to use only the offset in the data, we could initialize
the various sections separately. But then omapX_mux_init() would have
to know the partition number somehow..
After
Hi Tony,
On 9/27/2010 5:46 PM, Tony Lindgren wrote:
* Tony Lindgrent...@atomide.com [100924 17:14]:
* Benoit Coussonb-cous...@ti.com [100924 02:07]:
If we wanted to use only the offset in the data, we could initialize
the various sections separately. But then omapX_mux_init() would have
to
* Cousson, Benoit b-cous...@ti.com [100927 10:15]:
OK for that one, that will save the extra id to store the partition
in each static data, but then you will still have to store it during
the init?
For mux.c internal data, we can have an array of struct omap_mux_partition
that contains the
On 9/27/2010 7:36 PM, Tony Lindgren wrote:
* Cousson, Benoitb-cous...@ti.com [100927 10:15]:
OK for that one, that will save the extra id to store the partition
in each static data, but then you will still have to store it during
the init?
For mux.c internal data, we can have an array of
* Cousson, Benoit b-cous...@ti.com [100927 12:54]:
OK cool, let me know if I can help with something.
Thanks, but that should be fine for moment. I think I should have
the updated version before the end of the week.
OK
Just one clarification, I don't think we have to use two different
Hi Benoit,
* Benoit Cousson b-cous...@ti.com [100924 02:07]:
Starting on OMAP4, the pin mux configuration is located in two
different partitions of the control module (CODE_PAD and WKUP_PAD).
The first one is inside the core power domain whereas the second
one is inside the wakeup.
Since
