From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932719AbcIADpZ (ORCPT ); Wed, 31 Aug 2016 23:45:25 -0400 Received: from mail-pf0-f181.google.com ([209.85.192.181]:36288 "EHLO mail-pf0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754787AbcIADpV (ORCPT ); Wed, 31 Aug 2016 23:45:21 -0400 Subject: Re: [PATCH 2/4] cpu: expose pm_qos_resume_latency for each cpu To: Greg Kroah-Hartman References: <1472114562-2736-1-git-send-email-alex.shi@linaro.org> <1472114562-2736-2-git-send-email-alex.shi@linaro.org> <20160831131829.GB19101@kroah.com> <57C7A2FC.2030604@linaro.org> Cc: open list , linux-pm@vger.kernel.org, Ulf Hansson , Daniel Lezcano From: Alex Shi Message-ID: <57C7A44C.3000502@linaro.org> Date: Thu, 1 Sep 2016 11:45:16 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <57C7A2FC.2030604@linaro.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/01/2016 11:39 AM, Alex Shi wrote: > User can set values on each of cpu, like limit 100ms on cpu0, that means > the cpu0 response time should be in 100ms in possible idle. It similar > with DMA_LATENCY, but that request is for all cpu. This is just for > particular cpu, like a interrupt pined CPU. Sorry for typo! s/100ms/100us/ > > echo 100 > /sys/devices/system/cpu/cpu0/power/pm_qos_resume_latency_us >> >