From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751177AbcARFL3 (ORCPT ); Mon, 18 Jan 2016 00:11:29 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:59365 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750836AbcARFL1 (ORCPT ); Mon, 18 Jan 2016 00:11:27 -0500 Date: Sun, 17 Jan 2016 21:11:25 -0800 From: Greg Kroah-Hartman To: Dmitry Torokhov Cc: Rob Herring , Grant Likely , Linus Walleij , Thierry Reding , Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= , linux-kernel@vger.kernel.org, "Rafael J. Wysocki" Subject: Re: [PATCH] driver-core: platform: automatically mark wakeup devices Message-ID: <20160118051125.GA23372@kroah.com> References: <20160118021138.GA20498@dtor-ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160118021138.GA20498@dtor-ws> 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 On Sun, Jan 17, 2016 at 06:11:38PM -0800, Dmitry Torokhov wrote: > When probing platform drivers let's check if corresponding devices have > "wakeup-source" property defined (either in device tree, ACPI, or static > platform properties) and automatically enable such devices as wakeup > sources for the system. This will help us standardize on the name for this > property and reduce amount of boilerplate code in the drivers. How much boilerplate code can be removed? Do you have an example patch of this removal for any drivers if we move this logic into the driver core? thanks, greg k-h