[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdarPC+LxAAezT2LRiz=Y2RduUsb75YYHUgq7HqePzkD3Q@mail.gmail.com>
Date: Fri, 11 Oct 2013 10:14:29 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Sherman Yin <syin@...adcom.com>
Cc: Rob Herring <rob.herring@...xeda.com>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Stephen Warren <swarren@...dotorg.org>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Rob Landley <rob@...dley.net>,
Christian Daudt <bcm@...thebug.org>,
Russell King <linux@....linux.org.uk>,
Grant Likely <grant.likely@...aro.org>,
Matt Porter <matt.porter@...aro.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@...adcom.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 3/4] ARM: pinctrl: Add Broadcom Capri pinctrl driver
On Fri, Oct 11, 2013 at 1:48 AM, Sherman Yin <syin@...adcom.com> wrote:
>>> +static const struct capri_cfg_param capri_pinconf_params[] = {
>>> + {"brcm,hysteresis", CAPRI_PINCONF_PARAM_HYST},
>>> + {"brcm,pull", CAPRI_PINCONF_PARAM_PULL},
>>> + {"brcm,slew", CAPRI_PINCONF_PARAM_SLEW},
>>> + {"brcm,input_dis", CAPRI_PINCONF_PARAM_INPUT_DIS},
>>> + {"brcm,drive_str", CAPRI_PINCONF_PARAM_DRV_STR},
>>> + {"brcm,pull_up_str", CAPRI_PINCONF_PARAM_PULL_UP_STR},
>>> + {"brcm,mode", CAPRI_PINCONF_PARAM_MODE},
>>> +};
>>
>>As well as all this stuff...
>
> OK. Will see if I can find something suitable for "input disable" and "mode"
Let's discuss this. What exactly does "input disable" and "mode"
mean, in electrical terms?
When you come down to what actually happens it may turn out that
"input disable" is PIN_CONFIG_OUTPUT, which implicitly turns
off input does it not?
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists