From mboxrd@z Thu Jan 1 00:00:00 1970 From: b29396@freescale.com (Dong Aisheng) Date: Fri, 24 Aug 2012 10:28:09 +0800 Subject: [PATCH 1/7] mfd: add imx syscon driver based on regmap In-Reply-To: <20120823110647.GU7995@opensource.wolfsonmicro.com> References: <1345619928-15446-1-git-send-email-b29396@freescale.com> <1345619928-15446-2-git-send-email-b29396@freescale.com> <20120822160241.GR7995@opensource.wolfsonmicro.com> <20120823072629.GG10057@shlinux2.ap.freescale.net> <20120823110647.GU7995@opensource.wolfsonmicro.com> Message-ID: <20120824022807.GA5822@shlinux2.ap.freescale.net> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Aug 23, 2012 at 07:06:47PM +0800, Mark Brown wrote: > On Thu, Aug 23, 2012 at 03:26:30PM +0800, Dong Aisheng wrote: > > On Thu, Aug 23, 2012 at 12:02:41AM +0800, Mark Brown wrote: > > > > It'd be good to provide a way of retrieving the regmap so that drivers > > > for subsystems with generic regmap code could use the framework features > > > (regulator is one example that I just mentioned in my other mail). > > > Do you mean something like: > > regmap = syscon_regmap_dev_lookup(np, "fsl,anatop"); > > regmap_write(regmap, reg, val); > > > Then drivers can use generic regmap framework features rather than depend > > on what imx-syscon implemented, is that correct? > > Yes, this is mainly for cases where the subsystem has helper functions > that can work with regmap. Okay, then imx-syscon only implements regmap register mechanism and regmap lookup mechanism, for accessors, client driver can directly use the generic regmap API defined in include/linux/regmap.h. Then it looks to me the driver is more like a generic feature which may also be needed for other SoCs, IIRC, Tegra ahb and ux500 PRCMU, Do you think if we should implement it in a more generic way at first? e.g, drop 'imx-' prefix first. Linus, You're the first guy to raise the idea that we could implement a syscon framework to generic register access, what's your comment on this? Regards Dong Aisheng From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dong Aisheng Subject: Re: [PATCH 1/7] mfd: add imx syscon driver based on regmap Date: Fri, 24 Aug 2012 10:28:09 +0800 Message-ID: <20120824022807.GA5822@shlinux2.ap.freescale.net> References: <1345619928-15446-1-git-send-email-b29396@freescale.com> <1345619928-15446-2-git-send-email-b29396@freescale.com> <20120822160241.GR7995@opensource.wolfsonmicro.com> <20120823072629.GG10057@shlinux2.ap.freescale.net> <20120823110647.GU7995@opensource.wolfsonmicro.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20120823110647.GU7995-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: "devicetree-discuss" To: Mark Brown Cc: Zhao Richard-B20223 , "linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org" , "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org" , "s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org" , "kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org" , "lrg-l0cyMroinI0@public.gmane.org" , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , "sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org" List-Id: devicetree@vger.kernel.org On Thu, Aug 23, 2012 at 07:06:47PM +0800, Mark Brown wrote: > On Thu, Aug 23, 2012 at 03:26:30PM +0800, Dong Aisheng wrote: > > On Thu, Aug 23, 2012 at 12:02:41AM +0800, Mark Brown wrote: > > > > It'd be good to provide a way of retrieving the regmap so that drivers > > > for subsystems with generic regmap code could use the framework features > > > (regulator is one example that I just mentioned in my other mail). > > > Do you mean something like: > > regmap = syscon_regmap_dev_lookup(np, "fsl,anatop"); > > regmap_write(regmap, reg, val); > > > Then drivers can use generic regmap framework features rather than depend > > on what imx-syscon implemented, is that correct? > > Yes, this is mainly for cases where the subsystem has helper functions > that can work with regmap. Okay, then imx-syscon only implements regmap register mechanism and regmap lookup mechanism, for accessors, client driver can directly use the generic regmap API defined in include/linux/regmap.h. Then it looks to me the driver is more like a generic feature which may also be needed for other SoCs, IIRC, Tegra ahb and ux500 PRCMU, Do you think if we should implement it in a more generic way at first? e.g, drop 'imx-' prefix first. Linus, You're the first guy to raise the idea that we could implement a syscon framework to generic register access, what's your comment on this? Regards Dong Aisheng From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753663Ab2HXCrj (ORCPT ); Thu, 23 Aug 2012 22:47:39 -0400 Received: from am1ehsobe003.messaging.microsoft.com ([213.199.154.206]:46607 "EHLO am1outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751052Ab2HXCrf (ORCPT ); Thu, 23 Aug 2012 22:47:35 -0400 X-Forefront-Antispam-Report: CIP:70.37.183.190;KIP:(null);UIP:(null);IPV:NLI;H:mail.freescale.net;RD:none;EFVD:NLI X-SpamScore: 1 X-BigFish: VS1(zz98dI1432Izz1202h1082kzzz2dh2a8h668h839h944hd25hf0ah107ah1155h) Date: Fri, 24 Aug 2012 10:28:09 +0800 From: Dong Aisheng To: Mark Brown , CC: "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linus.walleij@stericsson.com" , "s.hauer@pengutronix.de" , "shawn.guo@linaro.org" , "kernel@pengutronix.de" , "grant.likely@secretlab.ca" , "rob.herring@calxeda.com" , "sameo@linux.intel.com" , "lrg@ti.com" , Zhao Richard-B20223 , "devicetree-discuss@lists.ozlabs.org" , "swarren@wwwdotorg.org" Subject: Re: [PATCH 1/7] mfd: add imx syscon driver based on regmap Message-ID: <20120824022807.GA5822@shlinux2.ap.freescale.net> References: <1345619928-15446-1-git-send-email-b29396@freescale.com> <1345619928-15446-2-git-send-email-b29396@freescale.com> <20120822160241.GR7995@opensource.wolfsonmicro.com> <20120823072629.GG10057@shlinux2.ap.freescale.net> <20120823110647.GU7995@opensource.wolfsonmicro.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20120823110647.GU7995@opensource.wolfsonmicro.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-OriginatorOrg: freescale.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 23, 2012 at 07:06:47PM +0800, Mark Brown wrote: > On Thu, Aug 23, 2012 at 03:26:30PM +0800, Dong Aisheng wrote: > > On Thu, Aug 23, 2012 at 12:02:41AM +0800, Mark Brown wrote: > > > > It'd be good to provide a way of retrieving the regmap so that drivers > > > for subsystems with generic regmap code could use the framework features > > > (regulator is one example that I just mentioned in my other mail). > > > Do you mean something like: > > regmap = syscon_regmap_dev_lookup(np, "fsl,anatop"); > > regmap_write(regmap, reg, val); > > > Then drivers can use generic regmap framework features rather than depend > > on what imx-syscon implemented, is that correct? > > Yes, this is mainly for cases where the subsystem has helper functions > that can work with regmap. Okay, then imx-syscon only implements regmap register mechanism and regmap lookup mechanism, for accessors, client driver can directly use the generic regmap API defined in include/linux/regmap.h. Then it looks to me the driver is more like a generic feature which may also be needed for other SoCs, IIRC, Tegra ahb and ux500 PRCMU, Do you think if we should implement it in a more generic way at first? e.g, drop 'imx-' prefix first. Linus, You're the first guy to raise the idea that we could implement a syscon framework to generic register access, what's your comment on this? Regards Dong Aisheng