From mboxrd@z Thu Jan 1 00:00:00 1970 From: heiko@sntech.de (Heiko =?iso-8859-1?q?St=FCbner?=) Date: Sun, 16 Jun 2013 12:45:29 +0200 Subject: [PATCH 1/5] pinctrl: update the documentation for some pinconfig params In-Reply-To: References: <201306141741.46077.heiko@sntech.de> <201306141742.21808.heiko@sntech.de> Message-ID: <201306161245.30465.heiko@sntech.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Am Sonntag, 16. Juni 2013, 12:26:38 schrieb Linus Walleij: > On Fri, Jun 14, 2013 at 5:42 PM, Heiko St?bner wrote: > > The BIAS_DISABLE and BIAS_HIGH_IMPEDANCE generic pinconfig options were > > missing information about their argument - which should be ignored. > > > > Also the BIAS_PULL_* options may have the pull strength as argument > > when they are activated, while simpler hardware can use any > > non-0 value for it. > > > > Update the kerneldoc to reflect this. > > > > Signed-off-by: Heiko Stuebner > > I'm holding this patch off. > > > * @PIN_CONFIG_BIAS_PULL_UP: the pin will be pulled up (usually with > > high > > > > - * impedance to VDD). If the argument is != 0 pull-up is enabled, > > - * if it is 0, pull-up is disabled. > > + * impedance to VDD). If the argument is != 0 pull-up is enabled. On > > + * hardware supporting this, the argument should contain the > > strength of + * the pull in Ohm. If it is 0, pull-up is disabled. > > As noted by Laurent, a pull-up of 0 Ohm is a short-circuit (bascially the > TOTAL pull-up) and it is pretty counter-intuitive to have that mean > "disable pull-up". Can we avoid this? > > > * @PIN_CONFIG_BIAS_PULL_DOWN: the pin will be pulled down (usually with > > high > > > > - * impedance to GROUND). If the argument is != 0 pull-down is > > enabled, - * if it is 0, pull-down is disabled. > > + * impedance to GROUND). If the argument is != 0 pull-down is > > enabled. On + * hardware supporting this, the argument should > > contain the strength of + * the pull in Ohm. If it is 0, pull-down > > is disabled. > > Dito. > > > * @PIN_CONFIG_BIAS_PULL_PIN_DEFAULT: the pin will be pulled up or down > > based * on embedded knowledge of the controller, like current mux > > function. > > > > - * If the argument is != 0 pull up/down is enabled, if it is 0, > > - * the pull is disabled. > > + * If the argument is != 0 pull up/down is enabled. On hardware > > supporting + * this, the argument should contain the strength of the > > pull in Ohm. + * If it is 0, pull is disabled. > > Dito. > > Can't we rely on PIN_CONFIG_BIAS_DISABLE for all this? you're the boss on this, I'll do whatever you say :-) I was going after the existing documentation of "bias-pull-X = <0>" being there to turn off this specific bias. So when reading the existing doc I was assuming somebody had needed this in the past. Actually I'm too more comfortable with only using bias-disable. So I'll redo this patch to remove the disabling of a pull via this method, if that's the right way to go. Same with the rockchip driver. Heiko From mboxrd@z Thu Jan 1 00:00:00 1970 From: Heiko =?iso-8859-1?q?St=FCbner?= Subject: Re: [PATCH 1/5] pinctrl: update the documentation for some pinconfig params Date: Sun, 16 Jun 2013 12:45:29 +0200 Message-ID: <201306161245.30465.heiko@sntech.de> References: <201306141741.46077.heiko@sntech.de> <201306141742.21808.heiko@sntech.de> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: 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: Linus Walleij Cc: James Hogan , "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Rob Herring , Laurent Pinchart , Grant Likely , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" List-Id: devicetree@vger.kernel.org Am Sonntag, 16. Juni 2013, 12:26:38 schrieb Linus Walleij: > On Fri, Jun 14, 2013 at 5:42 PM, Heiko St=FCbner wrote: > > The BIAS_DISABLE and BIAS_HIGH_IMPEDANCE generic pinconfig options were > > missing information about their argument - which should be ignored. > > = > > Also the BIAS_PULL_* options may have the pull strength as argument > > when they are activated, while simpler hardware can use any > > non-0 value for it. > > = > > Update the kerneldoc to reflect this. > > = > > Signed-off-by: Heiko Stuebner > = > I'm holding this patch off. > = > > * @PIN_CONFIG_BIAS_PULL_UP: the pin will be pulled up (usually with > > high > > = > > - * impedance to VDD). If the argument is !=3D 0 pull-up is enabled, > > - * if it is 0, pull-up is disabled. > > + * impedance to VDD). If the argument is !=3D 0 pull-up is enabled= . On > > + * hardware supporting this, the argument should contain the > > strength of + * the pull in Ohm. If it is 0, pull-up is disabled. > = > As noted by Laurent, a pull-up of 0 Ohm is a short-circuit (bascially the > TOTAL pull-up) and it is pretty counter-intuitive to have that mean > "disable pull-up". Can we avoid this? > = > > * @PIN_CONFIG_BIAS_PULL_DOWN: the pin will be pulled down (usually wi= th > > high > > = > > - * impedance to GROUND). If the argument is !=3D 0 pull-down is > > enabled, - * if it is 0, pull-down is disabled. > > + * impedance to GROUND). If the argument is !=3D 0 pull-down is > > enabled. On + * hardware supporting this, the argument should > > contain the strength of + * the pull in Ohm. If it is 0, pull-down > > is disabled. > = > Dito. > = > > * @PIN_CONFIG_BIAS_PULL_PIN_DEFAULT: the pin will be pulled up or down > > based * on embedded knowledge of the controller, like current mux > > function. > > = > > - * If the argument is !=3D 0 pull up/down is enabled, if it is 0, > > - * the pull is disabled. > > + * If the argument is !=3D 0 pull up/down is enabled. On hardware > > supporting + * this, the argument should contain the strength of the > > pull in Ohm. + * If it is 0, pull is disabled. > = > Dito. > = > Can't we rely on PIN_CONFIG_BIAS_DISABLE for all this? you're the boss on this, I'll do whatever you say :-) I was going after the existing documentation of "bias-pull-X =3D <0>" being = there to turn off this specific bias. So when reading the existing doc I wa= s = assuming somebody had needed this in the past. Actually I'm too more comfortable with only using bias-disable. So I'll redo this patch to remove the disabling of a pull via this method, = if = that's the right way to go. Same with the rockchip driver. Heiko From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755270Ab3FPKpf (ORCPT ); Sun, 16 Jun 2013 06:45:35 -0400 Received: from gloria.sntech.de ([95.129.55.99]:55944 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755148Ab3FPKpe (ORCPT ); Sun, 16 Jun 2013 06:45:34 -0400 From: Heiko =?iso-8859-1?q?St=FCbner?= To: Linus Walleij Subject: Re: [PATCH 1/5] pinctrl: update the documentation for some pinconfig params Date: Sun, 16 Jun 2013 12:45:29 +0200 User-Agent: KMail/1.13.7 (Linux/3.2.0-3-686-pae; KDE/4.8.4; i686; ; ) Cc: "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Grant Likely , Rob Herring , "devicetree-discuss@lists.ozlabs.org" , James Hogan , Laurent Pinchart References: <201306141741.46077.heiko@sntech.de> <201306141742.21808.heiko@sntech.de> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Message-Id: <201306161245.30465.heiko@sntech.de> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Sonntag, 16. Juni 2013, 12:26:38 schrieb Linus Walleij: > On Fri, Jun 14, 2013 at 5:42 PM, Heiko Stübner wrote: > > The BIAS_DISABLE and BIAS_HIGH_IMPEDANCE generic pinconfig options were > > missing information about their argument - which should be ignored. > > > > Also the BIAS_PULL_* options may have the pull strength as argument > > when they are activated, while simpler hardware can use any > > non-0 value for it. > > > > Update the kerneldoc to reflect this. > > > > Signed-off-by: Heiko Stuebner > > I'm holding this patch off. > > > * @PIN_CONFIG_BIAS_PULL_UP: the pin will be pulled up (usually with > > high > > > > - * impedance to VDD). If the argument is != 0 pull-up is enabled, > > - * if it is 0, pull-up is disabled. > > + * impedance to VDD). If the argument is != 0 pull-up is enabled. On > > + * hardware supporting this, the argument should contain the > > strength of + * the pull in Ohm. If it is 0, pull-up is disabled. > > As noted by Laurent, a pull-up of 0 Ohm is a short-circuit (bascially the > TOTAL pull-up) and it is pretty counter-intuitive to have that mean > "disable pull-up". Can we avoid this? > > > * @PIN_CONFIG_BIAS_PULL_DOWN: the pin will be pulled down (usually with > > high > > > > - * impedance to GROUND). If the argument is != 0 pull-down is > > enabled, - * if it is 0, pull-down is disabled. > > + * impedance to GROUND). If the argument is != 0 pull-down is > > enabled. On + * hardware supporting this, the argument should > > contain the strength of + * the pull in Ohm. If it is 0, pull-down > > is disabled. > > Dito. > > > * @PIN_CONFIG_BIAS_PULL_PIN_DEFAULT: the pin will be pulled up or down > > based * on embedded knowledge of the controller, like current mux > > function. > > > > - * If the argument is != 0 pull up/down is enabled, if it is 0, > > - * the pull is disabled. > > + * If the argument is != 0 pull up/down is enabled. On hardware > > supporting + * this, the argument should contain the strength of the > > pull in Ohm. + * If it is 0, pull is disabled. > > Dito. > > Can't we rely on PIN_CONFIG_BIAS_DISABLE for all this? you're the boss on this, I'll do whatever you say :-) I was going after the existing documentation of "bias-pull-X = <0>" being there to turn off this specific bias. So when reading the existing doc I was assuming somebody had needed this in the past. Actually I'm too more comfortable with only using bias-disable. So I'll redo this patch to remove the disabling of a pull via this method, if that's the right way to go. Same with the rockchip driver. Heiko