From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: AM33xx: PRM: Remove am33xx_pwrdm_read_prev_pwrst function
Date: Mon, 27 Nov 2017 08:59:42 -0800 [thread overview]
Message-ID: <20171127165942.GQ28152@atomide.com> (raw)
In-Reply-To: <1510313212-29660-1-git-send-email-j-keerthy@ti.com>
* Keerthy <j-keerthy@ti.com> [171110 03:29]:
> Referring TRM Am335X series:
> http://www.ti.com/lit/ug/spruh73p/spruh73p.pdf
>
> The LastPowerStateEntered bitfield is present only for PM_CEFUSE
> domain. This is not present in any of the other power domains. Hence
> remove the generic am33xx_pwrdm_read_prev_pwrst hook which wrongly
> reads the reserved bit fields for all the other power domains.
>
> Reading the reserved bits leads to wrongly interpreting the low
> power transitions for various power domains that do not have the
> LastPowerStateEntered field. The pm debug counters values are wrong
> currently as we are incrementing them based on the reserved bits.
>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
Applying into omap-for-v4.15/fixes thanks.
Tony
prev parent reply other threads:[~2017-11-27 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 11:26 [PATCH] ARM: AM33xx: PRM: Remove am33xx_pwrdm_read_prev_pwrst function Keerthy
2017-11-27 16:59 ` Tony Lindgren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171127165942.GQ28152@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).