Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753773Ab2BGFdZ (ORCPT ); Tue, 7 Feb 2012 00:33:25 -0500 Received: from hqemgate03.nvidia.com ([216.228.121.140]:19749 "EHLO hqemgate03.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752117Ab2BGFdY (ORCPT ); Tue, 7 Feb 2012 00:33:24 -0500 X-PGP-Universal: processed; by hqnvupgp07.nvidia.com on Mon, 06 Feb 2012 21:33:19 -0800 Message-ID: <4F30B79C.4030404@nvidia.com> Date: Mon, 06 Feb 2012 21:33:16 -0800 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111229 Thunderbird/9.0 MIME-Version: 1.0 To: Mitch Bradley CC: Dong Aisheng , Shawn Guo , Dong Aisheng-B29396 , "Linus Walleij (linus.walleij@linaro.org)" , "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 References: <74CDBE0F657A3D45AFBB94109FB122FF178E5D3160@HQMAIL01.nvidia.com> <4F302474.1020701@firmworks.com> In-Reply-To: <4F302474.1020701@firmworks.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2258 Lines: 51 On 02/06/2012 11:05 AM, Mitch Bradley wrote: > I like the general approach of simplifying the pinctrl thing, as the > previous approach did not appear to be converging. > > One possible name would be "gpconfig" - for general purpose configuration. Sounds reasonable > The register access model in the strawman proposal is probably too > simple. 32-bit memory mapped registers are certainly the most common > subcase on ARM, but there are many other cases that occur in practice: > > * Registers that must be accessed with 8, 16, or 64-bit cycles. > * Registers that have side effects on read, so read-mask-write must be > avoided > * Registers accessed via an index/data cycle pair, thus having locking > requirements > * Registers that must be read after being written, or otherwise > requiring some sort of memory-ordering enforcement. > * Time delays between pairs of writes > * PCI configuration registers, which often have some combination of the > above > * Registers behind serial buses like I2C > > Both Open Firmware and ACPI have addressed this general problem. In > addition to a numeric identifier for the register, you need to specify > the access semantics. It's difficult to finitely enumerate all possible > cases, but you can get to 99.9% with a modest number of access models, > and then add new models as needed. My thinking was that each driver that permitted execution of these register write sequences on its registers would provide an extremely simple driver to support this. Perhaps just one "op" function that implemented each write, and took care of details such as timing delays for the IO, indexed addressing, using I2C instead of memory-mapped, perhaps register access width, etc. Some of the items in the list above could be solved by explicit flags in the data instead (register access width comes to mind for memory-mapped devices at least). Do you have any direct pointers to how OF and ACPI solved this kind of thing; it'd be good background. -- nvpublic -- 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/