From: Jon Hunter <jon-hunter@ti.com>
To: Tony Lindgren <tony@atomide.com>, Benoit Cousson <b-cousson@ti.com>
Cc: device-tree <devicetree-discuss@lists.ozlabs.org>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
Jon Hunter <jon-hunter@ti.com>
Subject: [PATCH 2/5] ARM: OMAP: Force dmtimer restore if context loss is not detectable
Date: Tue, 19 Mar 2013 12:38:16 -0500 [thread overview]
Message-ID: <1363714699-29622-3-git-send-email-jon-hunter@ti.com> (raw)
In-Reply-To: <1363714699-29622-1-git-send-email-jon-hunter@ti.com>
When booting with device-tree the function pointer for detecting context
loss is not populated. Ideally, the pm_runtime framework should be
enhanced to allow a means for reporting context/state loss and we could
avoid populating such function pointers altogether. In the interim until
a generic non-device specific solution is in place, force a restore of
the dmtimer when enabling the timer.
Signed-off-by: Jon Hunter <jon-hunter@ti.com>
---
arch/arm/plat-omap/dmtimer.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/plat-omap/dmtimer.c b/arch/arm/plat-omap/dmtimer.c
index 5cae1dd..725d972 100644
--- a/arch/arm/plat-omap/dmtimer.c
+++ b/arch/arm/plat-omap/dmtimer.c
@@ -326,6 +326,8 @@ void omap_dm_timer_enable(struct omap_dm_timer *timer)
omap_timer_restore_context(timer);
timer->ctx_loss_count = c;
}
+ } else {
+ omap_timer_restore_context(timer);
}
}
}
--
1.7.10.4
WARNING: multiple messages have this Message-ID (diff)
From: jon-hunter@ti.com (Jon Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] ARM: OMAP: Force dmtimer restore if context loss is not detectable
Date: Tue, 19 Mar 2013 12:38:16 -0500 [thread overview]
Message-ID: <1363714699-29622-3-git-send-email-jon-hunter@ti.com> (raw)
In-Reply-To: <1363714699-29622-1-git-send-email-jon-hunter@ti.com>
When booting with device-tree the function pointer for detecting context
loss is not populated. Ideally, the pm_runtime framework should be
enhanced to allow a means for reporting context/state loss and we could
avoid populating such function pointers altogether. In the interim until
a generic non-device specific solution is in place, force a restore of
the dmtimer when enabling the timer.
Signed-off-by: Jon Hunter <jon-hunter@ti.com>
---
arch/arm/plat-omap/dmtimer.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/plat-omap/dmtimer.c b/arch/arm/plat-omap/dmtimer.c
index 5cae1dd..725d972 100644
--- a/arch/arm/plat-omap/dmtimer.c
+++ b/arch/arm/plat-omap/dmtimer.c
@@ -326,6 +326,8 @@ void omap_dm_timer_enable(struct omap_dm_timer *timer)
omap_timer_restore_context(timer);
timer->ctx_loss_count = c;
}
+ } else {
+ omap_timer_restore_context(timer);
}
}
}
--
1.7.10.4
next prev parent reply other threads:[~2013-03-19 17:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 17:38 [PATCH 0/5] ARM: OMAP: DMTIMER updates for v3.10 Jon Hunter
2013-03-19 17:38 ` Jon Hunter
[not found] ` <1363714699-29622-1-git-send-email-jon-hunter-l0cyMroinI0@public.gmane.org>
2013-03-19 17:38 ` [PATCH 1/5] ARM: OMAP: Simplify dmtimer context-loss handling Jon Hunter
2013-03-19 17:38 ` Jon Hunter
2013-03-19 17:38 ` Jon Hunter [this message]
2013-03-19 17:38 ` [PATCH 2/5] ARM: OMAP: Force dmtimer restore if context loss is not detectable Jon Hunter
2013-03-19 17:38 ` [PATCH 3/5] ARM: OMAP: Add function to request timer by node Jon Hunter
2013-03-19 17:38 ` Jon Hunter
2013-03-19 17:38 ` [PATCH 4/5] ARM: dts: OMAP2+: Update DMTIMER compatibility property Jon Hunter
2013-03-19 17:38 ` Jon Hunter
2013-03-19 17:38 ` [PATCH 5/5] ARM: OMAP2+: Populate DMTIMER errata when using device-tree Jon Hunter
2013-03-19 17:38 ` Jon Hunter
2013-04-04 18:38 ` [PATCH 0/5] ARM: OMAP: DMTIMER updates for v3.10 Tony Lindgren
2013-04-04 18:38 ` Tony Lindgren
2013-04-05 8:05 ` Benoit Cousson
2013-04-05 8:05 ` Benoit Cousson
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=1363714699-29622-3-git-send-email-jon-hunter@ti.com \
--to=jon-hunter@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.