[U-Boot] [PATCH v2 0/6] tegra2: Add more clock/pinmux functionality

[Simon Glass]

Hi Albert,

On Tue, Sep 27, 2011 at 9:04 AM, Simon Glass <sjg at chromium.org> wrote:
> Hi Albert,
>
> On Tue, Sep 27, 2011 at 12:21 AM, Albert ARIBAUD
> <albert.u.boot at aribaud.net> wrote:
>> Hi Simon,
>>
>> On 26/09/2011 19:06, Simon Glass wrote:
>>>
>>> Hi Albert,
>>>
>>> On Wed, Sep 21, 2011 at 3:40 PM, Simon Glass<sjg at chromium.org>  wrote:
>>>>
>>>> This adds to the basic clock functionality already available. The concept
>>>> of a peripheral ID is introduced, and all peripheral clock access is done
>>>> using this ID.
>>>>
>>>> Functions are provided to start, query and adjust peripheral clocks,
>>>> including automatic selection of the best available clock based on the
>>>> requested rate (this replaces hard-coded divisors).
>>>>
>>>> On the pinmux side we can now select functions for pin groups using the
>>>> new pinmux_set_func() function.
>>>>
>>>> Expanded functions are provided to adjust and query PLL clocks.
>>>>
>>>> With a full compliment of clock and pinmux functions, it should no longer
>>>> be necessary for board/driver code to directly access clock registers.
>>>> This
>>>> change removes all such accesses.
>>>>
>>>> This functionality will be used for I2C, SPI, LCD, USB, keyboard, NAND
>>>> and
>>>> other drivers for Tegra2.
>>>>
>>>> At then end is a patch to enable MMC on Seaboard, to make it all
>>>> worthwhile.
>>>>
>>>> Note: These patches include a definition of assert() which I will happily
>>>> remove if the one sent upstream is accepted.
>>>>
>>>> Changes in v2:
>>>> - Remove assert() which is now in common.h
>>>>
>>>> Simon Glass (6):
>>>>  tegra2: Rename CLOCK_PLL_ID to CLOCK_ID
>>>>  tegra2: Clean up board code a little
>>>>  tegra2: Add more clock functions
>>>>  tegra2: Rename PIN_ to PINGRP_
>>>>  tegra2: Add more pinmux functions
>>>>  tegra2: Enable MMC for Seaboard
>>>
>>> Are these ready to apply, do you think?
>>
>> They would appear to. Only these are not bug fixes, and so close to a
>> release, I am going to add them in /next, not /master.
>
> Yes, definitely /next, thanks.
>

Now that the release is over, is it possible to get these applied please?

Regards,
Simon