> Thanks applying 1 and 2 into omap-for-v3.9/board. Did not
> see patch 3 of this anywhere?
Thank you.
The third patch is for the TPS65910 PMU on the Craneboard.
It was already applied.
https://lkml.org/lkml/2012/11/30/192
Regards,
Milo
--
To unsubscribe from this list: send the line
Thanks applying 1 and 2 into omap-for-v3.9/board. Did not
see patch 3 of this anywhere?
Thank you.
The third patch is for the TPS65910 PMU on the Craneboard.
It was already applied.
https://lkml.org/lkml/2012/11/30/192
Regards,
Milo
--
To unsubscribe from this list: send the line unsubscribe
* Kim, Milo [121128 22:44]:
> This patch supports the TPS65910 PMU function on the AM3517 Craneboard.
> The IRQ pin, SYS_NIRQ is dedicated connection between the AM3517 and
> the TPS65910 PMU.
> To handle the PMU IRQs, mux configuration is required.
>
> Platform data configuration:
> .IRQ
* Kim, Milo milo@ti.com [121128 22:44]:
This patch supports the TPS65910 PMU function on the AM3517 Craneboard.
The IRQ pin, SYS_NIRQ is dedicated connection between the AM3517 and
the TPS65910 PMU.
To handle the PMU IRQs, mux configuration is required.
Platform data configuration:
This patch supports the TPS65910 PMU function on the AM3517 Craneboard.
The IRQ pin, SYS_NIRQ is dedicated connection between the AM3517 and
the TPS65910 PMU.
To handle the PMU IRQs, mux configuration is required.
Platform data configuration:
.IRQ number : SYS_NIRQ (M_IRQ_7)
.External
This patch supports the TPS65910 PMU function on the AM3517 Craneboard.
The IRQ pin, SYS_NIRQ is dedicated connection between the AM3517 and
the TPS65910 PMU.
To handle the PMU IRQs, mux configuration is required.
Platform data configuration:
.IRQ number : SYS_NIRQ (M_IRQ_7)
.External
6 matches
Mail list logo
