Govindraj writes:
> On Fri, Jun 18, 2010 at 11:53 PM, Kevin Hilman
> wrote:
>> Kevin Hilman writes:
>>
>>> "Govindraj.R" writes:
>>>
Changes from v1:
* Incorporated : OMAP clock: Add uart4_ick/fck definitions for 3630
* using omap_mux_request_signal to retreive padconf offset
>>
On Fri, Jun 18, 2010 at 11:53 PM, Kevin Hilman
wrote:
> Kevin Hilman writes:
>
>> "Govindraj.R" writes:
>>
>>> Changes from v1:
>>> * Incorporated : OMAP clock: Add uart4_ick/fck definitions for 3630
>>> * using omap_mux_request_signal to retreive padconf offset
>>> as per Tony's comments.
>>>
Kevin Hilman writes:
> "Govindraj.R" writes:
>
>> Changes from v1:
>> * Incorporated : OMAP clock: Add uart4_ick/fck definitions for 3630
>> * using omap_mux_request_signal to retreive padconf offset
>> as per Tony's comments.
>> http://marc.info/?l=linux-omap&m=127609369220618&w=2
>> This
"Govindraj.R" writes:
> Changes from v1:
> * Incorporated : OMAP clock: Add uart4_ick/fck definitions for 3630
> * using omap_mux_request_signal to retreive padconf offset
> as per Tony's comments.
> http://marc.info/?l=linux-omap&m=127609369220618&w=2
> This patch series as a dependecy on
Changes from v1:
* Incorporated : OMAP clock: Add uart4_ick/fck definitions for 3630
* using omap_mux_request_signal to retreive padconf offset
as per Tony's comments.
http://marc.info/?l=linux-omap&m=127609369220618&w=2
This patch series as a dependecy on the patch
for "omap_mux_request_si
