On Wed, May 7, 2014 at 9:59 AM, Nikita Kiryanov wrote:
>
> On 06/05/14 07:35, Tim Harvey wrote:
>>
>> On Tue, Apr 29, 2014 at 8:22 AM, Eric Nelson
>> wrote:
>
>
>
>>> The function name ..._array() also doesn't really capture what's
>>> going on here. Naming is hard though, and I'm not coming up
On 06/05/14 07:35, Tim Harvey wrote:
On Tue, Apr 29, 2014 at 8:22 AM, Eric Nelson
wrote:
The function name ..._array() also doesn't really capture what's
going on here. Naming is hard though, and I'm not coming up
with something else.
Perhaps 'sparse', 'skip', or alternate?
ya, I'm not sur
On Tue, Apr 29, 2014 at 8:22 AM, Eric Nelson
wrote:
> Hi Tim,
>
Hi Eric,
>
> On 04/28/2014 01:17 PM, Tim Harvey wrote:
>>
>>
>> Add new function that can take an array of iomux configs, an index, and
>> a stride to allow a multi-dimentional array of pinmux values to be used
>> to define pinmux v
Hi Tim,
On 04/28/2014 01:17 PM, Tim Harvey wrote:
>
Add new function that can take an array of iomux configs, an index, and
a stride to allow a multi-dimentional array of pinmux values to be used
to define pinmux values per cpu-type.
This takes a different approach to previously proposed soluti
Add new function that can take an array of iomux configs, an index, and
a stride to allow a multi-dimentional array of pinmux values to be used
to define pinmux values per cpu-type.
This takes a different approach to previously proposed solutions which used
multiple arrays of pad lists. The goal i
5 matches
Mail list logo