Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753949AbdHWLIY (ORCPT ); Wed, 23 Aug 2017 07:08:24 -0400 Received: from mail-wm0-f42.google.com ([74.125.82.42]:37525 "EHLO mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753760AbdHWLIW (ORCPT ); Wed, 23 Aug 2017 07:08:22 -0400 Date: Wed, 23 Aug 2017 19:08:10 +0800 From: Leo Yan To: Sudeep Holla Cc: Mathieu Poirier , Jonathan Corbet , linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Kim Phillips Subject: Re: [PATCH] doc: coresight: correct usage for '/dev/cpu_dma_latency' Message-ID: <20170823110810.GA28579@leoy-linaro> References: <1503472998-9009-1-git-send-email-leo.yan@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1480 Lines: 38 Hi Sudeep, On Wed, Aug 23, 2017 at 10:17:06AM +0100, Sudeep Holla wrote: > > On 23/08/17 08:23, Leo Yan wrote: > > In the coresight CPU debug document it suggests to use 'echo' command > > to set latency request to /dev/cpu_dma_latency so can disable all CPU > > idle states, but in fact this doesn't work. > > > > This is because when the command 'echo' exits, it releases the device > > node's file descriptor and the kernel release function removes the QoS > > constraint; finally when the command 'echo' finished there have no > > constraint imposed on cpu_dma_latency. > > > > This patch changes to use 'exec' to access '/dev/cpu_dma_latency', the > > command 'exec' can avoid the file descriptor to be closed so we can > > keep the constraint on cpu_dma_latency. > > > > This patch also corrects the description when set latency = 0uS, in > > this case the idle state0 still can be selected by CPUIdle governor so > > this means on ARM platform the 'WFI' state is still enabled, but all > > other deeper states have been disabled so CPUs will not be powered off. > > > > > IMO, we should just refer to cpuidle and PM QoS documents from here so > that any updates or changes in those documents are observed. Having a > copy of the text may result in it getting obsolete. Agree, we should point to below docs: Documentation/power/pm_qos_interface.txt, section 'From user mode'; Documentation/cpuidle/sysfs.txt; Thanks for good suggestion. > -- > Regards, > Sudeep