Re: [PATCH RFC 1/2] PM / Hibernate: use name_to_dev_t to parse resume

Quoting Sebastian Capella (2013-08-30 11:42:30) > Quoting Pavel Machek (2013-08-30 04:35:33) > > On Mon 2013-08-26 10:40:50, Sebastian Capella wrote: > > > Quoting Pavel Machek (2013-08-25 08:38:11) > > > > Is the allocation actually neccessary? At the very least thi

Re: [PATCH RFC 1/2] PM / Hibernate: use name_to_dev_t to parse resume

Quoting Pavel Machek (2013-08-30 04:35:33) > On Mon 2013-08-26 10:40:50, Sebastian Capella wrote: > > Quoting Pavel Machek (2013-08-25 08:38:11) > > > Is the allocation actually neccessary? At the very least this should > > > test for NULL... > > > > name

[PATCH v2 RFT 2/2] PM / Hibernate: add section for resume options

Expand the existing documentation to explicitly list the options for resuming a hibernation image, including the manual resume option which can be used from the initrd or initramfs and the kernel init resume. Signed-off-by: Sebastian Capella Cc: Rob Landley Cc: Len Brown Cc: Pavel Machek Cc

[PATCH v2 RFT 1/2] PM / Hibernate: use name_to_dev_t to parse resume

same syntax as the resume=device parameter, we can parse the resume=device in the init script and use the resume device directly from the kernel command line. Signed-off-by: Sebastian Capella Cc: Len Brown Cc: Pavel Machek Cc: "Rafael J. Wysocki" --- kernel/power/hib

[PATCH v2 RFT 0/2] PM / Hibernate: sysfs resume

Patchset related to hibernation resume: one enhancement to make the use of an existing file more general and one documentation update. Both patches are based on the 3.11-rc6 tag. This was tested on a Pandaboard with partial hibernation support, and compiled on x86. Further testing is needed on o

Re: [PATCH RFC 1/2] PM / Hibernate: use name_to_dev_t to parse resume

Apologies for my previous top post reply... Quoting Pavel Machek (2013-08-25 08:38:11) > Is the allocation actually neccessary? At the very least this should > test for NULL... Thanks Pavel! I'll add the check for NULL. name_to_dev_t expects a non-const name, but the buffer passed in is const.

Re: [PATCH RFC 1/2] PM / Hibernate: use name_to_dev_t to parse resume

well. By allowing > > /sys/debug/resume to accept the same syntax as the resume=device > > parameter, we can parse the resume=device in the init script and > > use the resume device directly from the kernel command line. > > > > Signed-off-by: Sebastian Capella &g

[PATCH RFC 2/2] PM / Hibernate: add section for resume options

Expand the existing documentation to explicitly list the options for resuming a hibernation image, including the manual resume option which can be used from the initrd or initramfs and the kernel init resume. Signed-off-by: Sebastian Capella --- Documentation/power/swsusp.txt | 15

[PATCH RFC 0/2] PM / Hibernate: sysfs resume

Patchset related to hibernation resume: one enhancement to make the use of an existing file more general and one documentation update. Both patches are based on the 3.11-rc6 tag. This was tested on a Pandaboard with partial hibernation support, and compiled on x86. Further testing is needed on o

[PATCH RFC 1/2] PM / Hibernate: use name_to_dev_t to parse resume

same syntax as the resume=device parameter, we can parse the resume=device in the init script and use the resume device directly from the kernel command line. Signed-off-by: Sebastian Capella --- kernel/power/hibernate.c | 14 +- 1 file changed, 9 insertions(+), 5 deletions(-) diff --

Re: [PATCH] cpuidle: arm_big_little: pass target residency to mcpm

Hi, I haven't heard back from anyone regarding my last request. If there are no objections, I'll go ahead and publish this patch to LKML and LAKML. Thanks, Sebastian On 29 May 2013 07:37, Sebastian Capella wrote: > Hi Guys, > > Sorry, I think the conversation went prett

Re: [PATCH] cpuidle: arm_big_little: pass target residency to mcpm

n for all of your time. Sebastian On 22 May 2013 11:51, Sebastian Capella wrote: > Quoting Dave Martin (2013-05-22 11:22:36) > > Currently not. This partly depends on whether the target residency is > > supposed to be a hint about the rough order of magnitude of the expected > &g

Re: [PATCH] cpuidle: arm_big_little: pass target residency to mcpm

Quoting Dave Martin (2013-05-22 11:22:36) > Currently not. This partly depends on whether the target residency is > supposed to be a hint about the rough order of magnitude of the expected > idle period, or whether it's supposed to be a strict contract. > > In effect, I think it's a hint which st

Re: [PATCH] cpuidle: arm_big_little: pass target residency to mcpm

Thanks Liviu! Some comments below.. Quoting Liviu Dudau (2013-05-21 10:15:42) > ... Which side of the interface are you actually thinking of? Both, I'm really just trying to understand the problem. > I don't think there is any C-state other than simple idle (which > translates into an WFI for t

Re: [PATCH] cpuidle: arm_big_little: pass target residency to mcpm

Hi Nico, Liviu, Catalin, Do you expect there to also be cases where the PSCI interface may not be aware of all of the platform states? Eg. if you have an SOC, not all of the cstates and latencies are directly related to the ARM core.. Maybe you can have additional states and latencies accounting

Re: [PATCH] cpuidle: arm_big_little: route target residency to mcpm

avior? Wouldn't it be worse to migrate to a lower c-state then we had intended? Thanks, Sebastian On 15 May 2013 10:07, Jon Medhurst (Tixy) wrote: > On Wed, 2013-05-15 at 09:49 -0700, Sebastian Capella wrote: > > Thanks Daniel! > > > > Liviu, > > > > I have b

Re: [PATCH] cpuidle: arm_big_little: route target residency to mcpm

Lezcano wrote: > On 05/15/2013 05:24 PM, Liviu Dudau wrote: > > Hi Sebastian, > > > > On Mon, May 13, 2013 at 07:53:42PM +0100, Sebastian Capella wrote: > >> Pass residency information to the mcpm_cpu_suspend. The information > >> is taken from the t

[PATCH] cpuidle: arm_big_little: route target residency to mcpm

maintained in the device tree and the vendor specific handling will then have enough information to determine what power state to enter without needing additional changes to the big_little framework. Signed-off-by: Sebastian Capella --- drivers/cpuidle/arm_big_little.c |6 -- 1 file changed

[PATCH] cpuidle: arm_big_little: pass target residency to mcpm

. Would someone be able to help verify this change on TC2? Thanks! Sebastian Sebastian Capella (1): cpuidle: arm_big_little: route target residency to mcpm drivers/cpuidle/arm_big_little.c |6 -- 1 file changed, 4 insertions(+), 2 deletions(-) -- 1.7.9.5

[PATCH: cpuidle: arm_big_little] pass target residency to mcpm

to help verify this change on TC2? Thanks! Sebastian Sebastian Capella (1): cpuidle: arm_big_little: route target residency to mcpm drivers/cpuidle/arm_big_little.c |6 -- 1 file changed, 4 insertions(+), 2 deletions(-) -- 1.7.9.5

[PATCH] cpuidle: arm_big_little: route target residency to mcpm

maintained in the device tree and the vendor specific handling will then have enough information to determine what power state to enter without needing additional changes to the big_little framework. Signed-off-by: Sebastian Capella --- drivers/cpuidle/arm_big_little.c |6 -- 1 file changed

Re: [PATCH powerdebug] clock: show only active clocks

Hi Sanjay, Also, clock tree dump (using powerdebug -dc) does not show the clock info anymore with this change. Thanks, Sebastian On 7 May 2013 15:05, Sebastian Capella wrote: > The original clock display in powerdebug would expand and collapse > subtrees in the clock heirarchy usi

Re: [PATCH powerdebug] clock: show only active clocks

The original clock display in powerdebug would expand and collapse subtrees in the clock heirarchy using the enter key. If we continue along the lines you're following, you'll want to override the actions in clock_select to do nothing as they're currently trying to expand the subtree which is caus