Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934031AbbENRvy (ORCPT ); Thu, 14 May 2015 13:51:54 -0400 Received: from muru.com ([72.249.23.125]:50995 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933364AbbENRvv (ORCPT ); Thu, 14 May 2015 13:51:51 -0400 Date: Thu, 14 May 2015 10:51:47 -0700 From: Tony Lindgren To: Felipe Balbi Cc: "Rafael J. Wysocki" , Alan Stern , Andreas Fenkart , Greg Kroah-Hartman , Huiquan Zhong , Kevin Hilman , NeilBrown , Mika Westerberg , Nishanth Menon , Peter Hurley , Sebastian Andrzej Siewior , Ulf Hansson , Thomas Gleixner , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org, linux-omap@vger.kernel.org Subject: Re: [PATCH 2/5] PM / Wakeirq: Add automated device wake IRQ handling Message-ID: <20150514175147.GN15563@atomide.com> References: <1431560196-5722-1-git-send-email-tony@atomide.com> <1431560196-5722-3-git-send-email-tony@atomide.com> <20150514020634.GB20006@saruman.tx.rr.com> <20150514155945.GL15563@atomide.com> <20150514160902.GF24269@saruman.tx.rr.com> <20150514162822.GM15563@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150514162822.GM15563@atomide.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1168 Lines: 33 * Tony Lindgren [150514 09:30]: > * Felipe Balbi [150514 09:12]: > > > > int dev_pm_request_wake_irq_managed(struct device *dev, int irq); > > > > I don't get this. Would this request with devm_ while the former > > wouldn't use devm_ ? > > Typo :) Both can be devm no problem. ... > > > The life cycle of the request and free of the wake irq is not the > > > same as the life cycle of the device driver. For example, serial > > > drivers can request interrupts on startup and free them on shutdown. > > > > fair enough, but then we start to consider the benefits of using > > devm_ IRQ :-) > > Hmm probably the extra checks do not hurt there either. We should keep the PM related functions called dev_pm_*, using devm_pm_* just gets hard to pronounce.. So yeah I too am thinking just not using devm here at all as the consumer drivers are not allocating anything. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/