Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758657Ab2HUVis (ORCPT ); Tue, 21 Aug 2012 17:38:48 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:46568 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758482Ab2HUVin (ORCPT ); Tue, 21 Aug 2012 17:38:43 -0400 Message-ID: <5033FFE0.5070209@wwwdotorg.org> Date: Tue, 21 Aug 2012 15:38:40 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: Linus Walleij CC: Thomas Abraham , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, grant.likely@secretlab.ca, rob.herring@calxeda.com, kgene.kim@samsung.com, Dong Aisheng Subject: Re: [PATCH v2 1/4] pinctrl: add samsung pinctrl and gpiolib driver References: <1345060656-32201-1-git-send-email-thomas.abraham@linaro.org> <1345060656-32201-2-git-send-email-thomas.abraham@linaro.org> In-Reply-To: X-Enigmail-Version: 1.5a1pre 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: 1900 Lines: 39 On 08/21/2012 05:25 AM, Linus Walleij wrote: > On Wed, Aug 15, 2012 at 9:57 PM, Thomas Abraham > wrote: > >> Add a new device tree enabled pinctrl and gpiolib driver for Samsung >> SoC's. ... >> + The child node can also optionally specify one or more of the pin >> + configuration that should be applied on all the pins listed in the >> + "samsung,pins" property of the child node. The following pin configuration >> + properties are supported. >> + >> + - samsung,pin-pud: Pull up/down configuration. >> + - samsung,pin-drv: Drive strength configuration. >> + - samsung,pin-pud-pdn: Pull up/down configuration in power down mode. >> + - samsung,pin-drv-pdn: Drive strength configuration in power down mode. > > This looks a bit scary, as it seems to be orthogonal to the pin config > interface. I.e. this will be programmed "behind the back" of the > pin config system. However as long as the pin config implementation > reads back these things from the registers it will work, too. > > In the U300 and Ux500 I explicitly use pin config hogs to set up > the pin configuration, and when we enter a state such as > "default" the mux setting and config settings are set from the > framework separately. I know that some HW has a separate set of registers (or fields) for the "awake" and "sleep" configuration, and the HW switches between the two automatically when sleeping. I have no idea if the Samsung SoCs do this, but I think if this were the case, it'd be quite legitimate to define both these HW states as separate sets of properties within a single pinctrl SW state. So, that might be the explanation here? -- 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/