Hi Paul,
On Tue, 2012-10-16 at 07:29 +, Paul Walmsley wrote:
Hi Kevin,
Here's an updated version of this one, with the erratum coverage expanded
to include OMAP34xx/35xx.
I think this one can replace Tero's [PATCHv6 06/11] ARM: OMAP:
clockdomain: add support for preventing autodep
Hi Kevin,
Here's an updated version of this one, with the erratum coverage expanded
to include OMAP34xx/35xx.
I think this one can replace Tero's [PATCHv6 06/11] ARM: OMAP:
clockdomain: add support for preventing autodep delete and [PATCHv6
07/11] ARM: OMAP3: do not delete per_clkdm autodeps
Paul Walmsley p...@pwsan.com writes:
Hi Kevin,
Here's an updated version of this one, with the erratum coverage expanded
to include OMAP34xx/35xx.
I think this one can replace Tero's [PATCHv6 06/11] ARM: OMAP:
clockdomain: add support for preventing autodep delete and [PATCHv6
07/11]
On Tue, 2012-09-18 at 22:25 +, Paul Walmsley wrote:
Hi Tero,
just looking at the usecounting series to see what is mergeable and
noticed this:
On Fri, 13 Jul 2012, Tero Kristo wrote:
Secondly, there are multiple erratas for omap3, which say that the
wakedeps should be enabled
Paul Walmsley p...@pwsan.com writes:
On Tue, 18 Sep 2012, Paul Walmsley wrote:
What do you think about the following patch to handle part of the i582
workaround?
That patch was an older version; here's one that builds and boots - sorry
about that. It passed the basic PM tests here on
Hi Tero,
just looking at the usecounting series to see what is mergeable and
noticed this:
On Fri, 13 Jul 2012, Tero Kristo wrote:
Secondly, there are multiple erratas for omap3, which say that the
wakedeps should be enabled for the PER domain, see e.g. errata i582 for
omap3630.
Erratum
On Tue, 18 Sep 2012, Paul Walmsley wrote:
What do you think about the following patch to handle part of the i582
workaround?
That patch was an older version; here's one that builds and boots - sorry
about that. It passed the basic PM tests here on 3730ES1.0 Beagle XM and
3730ES1.2 EVM.
Previously, PER clock domain was always enabled, as the usecounts
for this domain incorrectly always showed positive value. On HW
level though, the domain enters idle as it is set in HW supervised
mode. Now, when the usecounts reflect real values, PER domain
will be put to HWSUP sleep mode, which
