Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp5256912ybi; Tue, 30 Jul 2019 17:13:14 -0700 (PDT) X-Google-Smtp-Source: APXvYqz6Lm5tDRq/1GWatt234+Tzlb+5LPgwje1FRdjwAAFUoSrVdF763aNYJKalp12W3S53LbTM X-Received: by 2002:a62:f250:: with SMTP id y16mr44207151pfl.50.1564531993987; Tue, 30 Jul 2019 17:13:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564531993; cv=none; d=google.com; s=arc-20160816; b=y2yoe+Z1hCMkhSPpnpbYQhKXfwVOh6OTod8hf1itDDJp8LpbCtJ4hRPCB7L9RU9XU0 BIvzJB4UO3A/pwV1aHvqXQ+rx5S1s5JmhH6wYJlKVTRyqcQEmnkimViFPY70TY+S5t2J EATxWH8i5a7CuhdYQZkZeLfpmLCiD0KsjLv2dkx8SdBPkqnBJzxIUTxWWnXJZ6zL7T8w DvMUHhb3Y6ZZaV2S6vL5rnMcN/hddlS+zpWO6fT0+jhZNdn6TsA9cofVPS6lGGyvho9E UAVZ8EjXSSTuWTJUc1QNqyllom62bjrh9+DCWStc/G030rsjcVVB0qTfZEjHWpwQzkv3 7e9Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=31Id38azHvty3E7MmgQycdSsnXLO3Gnlc8jtivnraKE=; b=y39oaq3r5Z+DUnvTJl1DJDGw7ee89dzADTxO+EYFRZkEFosL6K8BgD4dq239lvjOkw xWIhTHQbbKceDU0eS1jIHVvK0HK1S9PHxD0Uz6uVHzHsWcpRUhG3Y1yr+5EoRvHqss0g dHBhYnChdRv5r6GgvjQF8j2YqtHZNWwYZV/UUOR7IY8xf7JJCNVpGx9b6k49CnkMdmsD D0thA79AiOoAlLp87Sgkt3rKUIXys5R9ZuWmFk9I2KpKxxzmoYegAf5oRBCvTaSH0cQo 5O9FCqiAukaIY/qBfL6vxrwcg2wGIpHybeMVmk1MFO6iRz1GMGf+GtbeeRLF76DKJpND +gZQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q14si31109367pgm.325.2019.07.30.17.12.58; Tue, 30 Jul 2019 17:13:13 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729056AbfG3WR6 (ORCPT + 99 others); Tue, 30 Jul 2019 18:17:58 -0400 Received: from cloudserver094114.home.pl ([79.96.170.134]:60241 "EHLO cloudserver094114.home.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727221AbfG3WR6 (ORCPT ); Tue, 30 Jul 2019 18:17:58 -0400 Received: from 79.184.255.110.ipv4.supernova.orange.pl (79.184.255.110) (HELO kreacher.localnet) by serwer1319399.home.pl (79.96.170.134) with SMTP (IdeaSmtpServer 0.83.275) id 0ed09bd7b97d5494; Wed, 31 Jul 2019 00:17:56 +0200 From: "Rafael J. Wysocki" To: Stephen Boyd Cc: "Rafael J. Wysocki" , Tri Vo , Greg Kroah-Hartman , Viresh Kumar , Hridya Valsaraju , Sandeep Patil , Kalesh Singh , Ravi Chandra Sadineni , Linux Kernel Mailing List , Linux PM , "Cc: Android Kernel" , kbuild test robot Subject: Re: [PATCH v5] PM / wakeup: show wakeup sources stats in sysfs Date: Wed, 31 Jul 2019 00:17:55 +0200 Message-ID: <2085893.cJkfNvi94x@kreacher> In-Reply-To: <5d4090ea.1c69fb81.d5cab.4dcd@mx.google.com> References: <20190730024309.233728-1-trong@android.com> <5d4090ea.1c69fb81.d5cab.4dcd@mx.google.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday, July 30, 2019 8:48:09 PM CEST Stephen Boyd wrote: > Quoting Tri Vo (2019-07-30 11:39:34) > > On Mon, Jul 29, 2019 at 10:46 PM Rafael J. Wysocki wrote: > > > > > > On Tue, Jul 30, 2019 at 4:45 AM Tri Vo wrote: > > > > - Device registering the wakeup source is now the parent of the wakeup source. > > > > Updated wakeup_source_register()'s signature and its callers accordingly. > > > > > > And I really don't like these changes. Especially having "wakeup" > > > twice in the path. > > > > I can trim it down to /sys/class/wakeup//. Does that sound good? > > Using the same prefix for the class and the device name is quite common. > For example, see the input, regulator, tty, tpm, remoteproc, hwmon, > extcon classes. I'd prefer it was left as /sys/class/wakeup/wakeupN. The > class name could be changed to wakeup_source perhaps (i.e. > /sys/class/wakeup_source/wakeupN)? Alternatively /sys/class/wakeup/wsN