From mboxrd@z Thu Jan 1 00:00:00 1970 From: broonie@opensource.wolfsonmicro.com (Mark Brown) Date: Mon, 6 Feb 2012 19:41:25 +0000 Subject: An extremely simplified pinctrl bindings proposal In-Reply-To: <4F2F6AE2.1040504@nvidia.com> References: <74CDBE0F657A3D45AFBB94109FB122FF178E5D3160@HQMAIL01.nvidia.com> <4F2F6AE2.1040504@nvidia.com> Message-ID: <20120206194125.GA23030@sirena.org.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Sun, Feb 05, 2012 at 09:53:38PM -0800, Stephen Warren wrote: > On 02/05/2012 08:20 PM, Linus Walleij wrote: > > A controlled set of register read/writes and maybe also conditionals > > (if that bit is 1, do this, else do that, plus a loop command to wait > > for a flag or similar) are known as a "jam tables" and usually used > > in BIOSes to do a compact machine initialization. I learned this term > > in Bunnie Huang's "Hacking the Xbox, where he describes finding a > > jam table interpreter in the Xbox ROM. FWIW I just added a subset of this functionality (called "patches" for want of a better name) to regmap, just a simple list of register writes that get blasted in htere. The intent is somewhat different, though - it's there for dumping undocumented or partially documented register write sequences from vendors into devices since there's a common pattern of doing that when bringing things out of reset, more like what Grant seems to have been talking about in that thread. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: An extremely simplified pinctrl bindings proposal Date: Mon, 6 Feb 2012 19:41:25 +0000 Message-ID: <20120206194125.GA23030@sirena.org.uk> References: <74CDBE0F657A3D45AFBB94109FB122FF178E5D3160@HQMAIL01.nvidia.com> <4F2F6AE2.1040504@nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <4F2F6AE2.1040504-DDmLM1+adcrQT0dZR+AlfA@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-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org To: Stephen Warren Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org" , "cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org" , Dong Aisheng , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org" , "kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org" , "Sascha Hauer (s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org)" , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" List-Id: devicetree@vger.kernel.org On Sun, Feb 05, 2012 at 09:53:38PM -0800, Stephen Warren wrote: > On 02/05/2012 08:20 PM, Linus Walleij wrote: > > A controlled set of register read/writes and maybe also conditionals > > (if that bit is 1, do this, else do that, plus a loop command to wait > > for a flag or similar) are known as a "jam tables" and usually used > > in BIOSes to do a compact machine initialization. I learned this term > > in Bunnie Huang's "Hacking the Xbox, where he describes finding a > > jam table interpreter in the Xbox ROM. FWIW I just added a subset of this functionality (called "patches" for want of a better name) to regmap, just a simple list of register writes that get blasted in htere. The intent is somewhat different, though - it's there for dumping undocumented or partially documented register write sequences from vendors into devices since there's a common pattern of doing that when bringing things out of reset, more like what Grant seems to have been talking about in that thread. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754998Ab2BFTls (ORCPT ); Mon, 6 Feb 2012 14:41:48 -0500 Received: from cassiel.sirena.org.uk ([80.68.93.111]:49167 "EHLO cassiel.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751935Ab2BFTlr (ORCPT ); Mon, 6 Feb 2012 14:41:47 -0500 Date: Mon, 6 Feb 2012 19:41:25 +0000 From: Mark Brown To: Stephen Warren Cc: Linus Walleij , Dong Aisheng , Shawn Guo , Dong Aisheng-B29396 , "Sascha Hauer (s.hauer@pengutronix.de)" , "rob.herring@calxeda.com" , "kernel@pengutronix.de" , "cjb@laptop.org" , "Simon Glass (sjg@chromium.org)" , Thomas Abraham , "Grant Likely (grant.likely@secretlab.ca)" , "ext Tony Lindgren (tony@atomide.com)" , "devicetree-discuss@lists.ozlabs.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: An extremely simplified pinctrl bindings proposal Message-ID: <20120206194125.GA23030@sirena.org.uk> References: <74CDBE0F657A3D45AFBB94109FB122FF178E5D3160@HQMAIL01.nvidia.com> <4F2F6AE2.1040504@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F2F6AE2.1040504@nvidia.com> X-Cookie: Don't feed the bats tonight. User-Agent: Mutt/1.5.20 (2009-06-14) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: broonie@sirena.org.uk X-SA-Exim-Scanned: No (on cassiel.sirena.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Feb 05, 2012 at 09:53:38PM -0800, Stephen Warren wrote: > On 02/05/2012 08:20 PM, Linus Walleij wrote: > > A controlled set of register read/writes and maybe also conditionals > > (if that bit is 1, do this, else do that, plus a loop command to wait > > for a flag or similar) are known as a "jam tables" and usually used > > in BIOSes to do a compact machine initialization. I learned this term > > in Bunnie Huang's "Hacking the Xbox, where he describes finding a > > jam table interpreter in the Xbox ROM. FWIW I just added a subset of this functionality (called "patches" for want of a better name) to regmap, just a simple list of register writes that get blasted in htere. The intent is somewhat different, though - it's there for dumping undocumented or partially documented register write sequences from vendors into devices since there's a common pattern of doing that when bringing things out of reset, more like what Grant seems to have been talking about in that thread.