Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758294Ab3JKQBv (ORCPT ); Fri, 11 Oct 2013 12:01:51 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:10371 "EHLO mho-02-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753823Ab3JKQBt (ORCPT ); Fri, 11 Oct 2013 12:01:49 -0400 X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 50.131.214.131 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1834I1FYJLkDuGpmAiwli2M Date: Fri, 11 Oct 2013 09:01:46 -0700 From: Tony Lindgren To: Linus Walleij Cc: Roger Quadros , "linux-arm-kernel@lists.infradead.org" , "devicetree@vger.kernel.org" , Grygorii Strashko , "linux-kernel@vger.kernel.org" , Peter Ujfalusi , Prakash Manjunathappa , Haojian Zhuang , =?utf-8?Q?Beno=C3=AEt?= Cousson , Linux-OMAP Subject: Re: [PATCH 4/6] pinctrl: single: Add support for wake-up interrupts Message-ID: <20131011160146.GR29913@atomide.com> References: <20131003054221.8941.87801.stgit@localhost> <5256AA7F.8030005@ti.com> <20131010160018.GA29913@atomide.com> <20131010162015.GC29913@atomide.com> <5257BD3E.5000707@ti.com> <20131011154352.GO29913@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1437 Lines: 32 * Linus Walleij [131011 09:05]: > On Fri, Oct 11, 2013 at 5:43 PM, Tony Lindgren wrote: > > * Linus Walleij [131011 03:40]: > >> On Fri, Oct 11, 2013 at 10:56 AM, Roger Quadros wrote: > >> > >> > The register handling is fine. But how do we deal with resource handling? > >> > e.g. the block that has the deep-core registers might need to be clocked or powered > >> > before the registers can be accessed. > >> > >> Yeah I saw this in the code there. > >> > >> In this case it seems syscon-type regmap access can be used to > >> read/write the registers, so maybe the pin controller also need to > >> get a handle on some clock etc? > > > > Uhh, let's not go there.. The resource availability needs to be > > handled transparently in regmap code and the reg provider hardware > > module driver using runtime PM. > > OK we can surely discuss this with broonie, it makes sense to > have regmap be able to do its deed transparently. Yes I think so too. Sounds like we need callbacks for the runtime PM checks to the "register provider" driver. Hwo knows, maybe those features are there already :) 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/