From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Linux-sh list" <linux-sh@vger.kernel.org>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>
Subject: [PATCH 3/4] PM / shmobile: Specify device latencies for SH7372 devices directly
Date: Wed, 8 Aug 2012 00:28:36 +0200 [thread overview]
Message-ID: <201208080028.36688.rjw@sisk.pl> (raw)
In-Reply-To: <201208080026.01738.rjw@sisk.pl>
The results of adaptive latency computations in
GENPD_DEV_TIMED_CALLBACK() show that the start/stop and save/restore
state latencies of all devices on SH7372 I have tried are a little
below 250 us. Therefore, if the 250 us is used as the common initial
value of the latency fields in struct gpd_timing_data for all devices
on SH7372, the latency values will never have to change at run time
and there won't be any overhead related to re-computation of the
corresponding PM QoS data.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
---
arch/arm/mach-shmobile/setup-sh7372.c | 57 +++++++++++++++++++---------------
1 file changed, 33 insertions(+), 24 deletions(-)
Index: linux/arch/arm/mach-shmobile/setup-sh7372.c
===================================================================
--- linux.orig/arch/arm/mach-shmobile/setup-sh7372.c
+++ linux/arch/arm/mach-shmobile/setup-sh7372.c
@@ -999,8 +999,17 @@ static struct platform_device *sh7372_la
&spu1_device,
};
+#define DEV_LATENCY_NS 250000
+
void __init sh7372_add_standard_devices(void)
{
+ struct gpd_timing_data latencies = {
+ .stop_latency_ns = DEV_LATENCY_NS,
+ .start_latency_ns = DEV_LATENCY_NS,
+ .save_state_latency_ns = DEV_LATENCY_NS,
+ .restore_state_latency_ns = DEV_LATENCY_NS,
+ };
+
sh7372_init_pm_domains();
platform_add_devices(sh7372_early_devices,
@@ -1009,30 +1018,30 @@ void __init sh7372_add_standard_devices(
platform_add_devices(sh7372_late_devices,
ARRAY_SIZE(sh7372_late_devices));
- rmobile_add_device_to_domain("A3RV", &vpu_device);
- rmobile_add_device_to_domain("A4MP", &spu0_device);
- rmobile_add_device_to_domain("A4MP", &spu1_device);
- rmobile_add_device_to_domain("A3SP", &scif0_device);
- rmobile_add_device_to_domain("A3SP", &scif1_device);
- rmobile_add_device_to_domain("A3SP", &scif2_device);
- rmobile_add_device_to_domain("A3SP", &scif3_device);
- rmobile_add_device_to_domain("A3SP", &scif4_device);
- rmobile_add_device_to_domain("A3SP", &scif5_device);
- rmobile_add_device_to_domain("A3SP", &scif6_device);
- rmobile_add_device_to_domain("A3SP", &iic1_device);
- rmobile_add_device_to_domain("A3SP", &dma0_device);
- rmobile_add_device_to_domain("A3SP", &dma1_device);
- rmobile_add_device_to_domain("A3SP", &dma2_device);
- rmobile_add_device_to_domain("A3SP", &usb_dma0_device);
- rmobile_add_device_to_domain("A3SP", &usb_dma1_device);
- rmobile_add_device_to_domain("A4R", &iic0_device);
- rmobile_add_device_to_domain("A4R", &veu0_device);
- rmobile_add_device_to_domain("A4R", &veu1_device);
- rmobile_add_device_to_domain("A4R", &veu2_device);
- rmobile_add_device_to_domain("A4R", &veu3_device);
- rmobile_add_device_to_domain("A4R", &jpu_device);
- rmobile_add_device_to_domain("A4R", &tmu00_device);
- rmobile_add_device_to_domain("A4R", &tmu01_device);
+ rmobile_add_device_to_domain_td("A3RV", &vpu_device, &latencies);
+ rmobile_add_device_to_domain_td("A4MP", &spu0_device, &latencies);
+ rmobile_add_device_to_domain_td("A4MP", &spu1_device, &latencies);
+ rmobile_add_device_to_domain_td("A3SP", &scif0_device, &latencies);
+ rmobile_add_device_to_domain_td("A3SP", &scif1_device, &latencies);
+ rmobile_add_device_to_domain_td("A3SP", &scif2_device, &latencies);
+ rmobile_add_device_to_domain_td("A3SP", &scif3_device, &latencies);
+ rmobile_add_device_to_domain_td("A3SP", &scif4_device, &latencies);
+ rmobile_add_device_to_domain_td("A3SP", &scif5_device, &latencies);
+ rmobile_add_device_to_domain_td("A3SP", &scif6_device, &latencies);
+ rmobile_add_device_to_domain_td("A3SP", &iic1_device, &latencies);
+ rmobile_add_device_to_domain_td("A3SP", &dma0_device, &latencies);
+ rmobile_add_device_to_domain_td("A3SP", &dma1_device, &latencies);
+ rmobile_add_device_to_domain_td("A3SP", &dma2_device, &latencies);
+ rmobile_add_device_to_domain_td("A3SP", &usb_dma0_device, &latencies);
+ rmobile_add_device_to_domain_td("A3SP", &usb_dma1_device, &latencies);
+ rmobile_add_device_to_domain_td("A4R", &iic0_device, &latencies);
+ rmobile_add_device_to_domain_td("A4R", &veu0_device, &latencies);
+ rmobile_add_device_to_domain_td("A4R", &veu1_device, &latencies);
+ rmobile_add_device_to_domain_td("A4R", &veu2_device, &latencies);
+ rmobile_add_device_to_domain_td("A4R", &veu3_device, &latencies);
+ rmobile_add_device_to_domain_td("A4R", &jpu_device, &latencies);
+ rmobile_add_device_to_domain_td("A4R", &tmu00_device, &latencies);
+ rmobile_add_device_to_domain_td("A4R", &tmu01_device, &latencies);
}
static void __init sh7372_earlytimer_init(void)
next prev parent reply other threads:[~2012-08-08 9:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-21 21:49 [RFC][PATCH 0/5] PM / shmobile: Specify PM domain and device latency information directly Rafael J. Wysocki
2012-07-21 21:53 ` [RFC][PATCH 1/5] PM / shmobile: Set SH7372 PM domain on/off latencies directly Rafael J. Wysocki
2012-07-21 21:54 ` [RFC][PATCH 2/5] PM / shmobile: Allow device latencies to be specified directly Rafael J. Wysocki
2012-07-21 21:54 ` [RFC][PATCH 3/5] PM / shmobile: Specify device latencies for SH7372 devices directly Rafael J. Wysocki
2012-07-21 21:55 ` [RFC][PATCH 4/5] PM / shmobile: Specify device latencies for Mackerel " Rafael J. Wysocki
2012-07-21 21:56 ` [RFC][PATCH 5/5] PM / shmobile: Allow device latencies to be read from a DT Rafael J. Wysocki
2012-08-07 22:26 ` [PATCH 0/4] PM / shmobile: Specify PM domain and device latency information directly Rafael J. Wysocki
2012-08-07 22:27 ` [PATCH 1/4] PM / shmobile: Set PM domain on/off latencies directly Rafael J. Wysocki
2012-08-07 22:27 ` [PATCH 2/4] PM / shmobile: Allow device latencies to be specified directly Rafael J. Wysocki
2012-08-07 22:28 ` Rafael J. Wysocki [this message]
2012-08-07 22:29 ` [PATCH 4/4] PM / shmobile: Specify device latencies for Mackerel devices directly Rafael J. Wysocki
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=201208080028.36688.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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 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).