From: Linus Walleij <linus.walleij@linaro.org>
To: Ludovic Desroches <ludovic.desroches@microchip.com>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-gpio@vger.kernel.org,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: at91-pio4: add support for drive-strength property
Date: Mon, 22 Jan 2018 09:37:38 +0100 [thread overview]
Message-ID: <CACRpkdanweSmHd_M+feHauEHtvKSW+-W=djb186BFdbxTf20Jg@mail.gmail.com> (raw)
In-Reply-To: <20180118160208.16461-1-ludovic.desroches@microchip.com>
On Thu, Jan 18, 2018 at 5:02 PM, Ludovic Desroches
<ludovic.desroches@microchip.com> wrote:
> Add support for the drive-strength property. Usually its value is
> expressed in mA. Since the numeric value depends on VDDIOP voltage,
> the controller uses low, medium and high to define the drive-strengh.
Aha I see. That's complex. It certainly results in a certain mA drive
strength in the end, but what you're saying is that this is not usually
what we configure.
> The PIO controller accepts two values for the low drive: 0 or 1. Most
> of the time, we don't care about the drive strength, there is no need
> to change it, so 0 is considered as the default value.
Do you mean default value as in "whatever the hardware was set
up as at boot time"?
> The low-drive
> value won't be advertised through pinconf-pins file excepted if it
except?
> has been set explicitly in the device tree ie if its value is
> different from 0.
>
> Signed-off-by: Ludovic Desroches <ludovic.desroches@microchip.com>
OK I think I get it.
> Optional properties:
> - GENERIC_PINCONFIG: generic pinconfig options to use, bias-disable,
> -bias-pull-down, bias-pull-up, drive-open-drain, input-schmitt-enable,
> -input-debounce, output-low, output-high.
> +bias-pull-down, bias-pull-up, drive-open-drain, drive-strength,
> +input-schmitt-enable, input-debounce, output-low, output-high.
(...)
> + drive-strength = <ATMEL_PIO_DRVSTR_LO>;
So you say you support this argument and it will be something like
include/dt-bindings/pinctrl/at91.h:#define ATMEL_PIO_DRVSTR_LO 1
include/dt-bindings/pinctrl/at91.h:#define ATMEL_PIO_DRVSTR_ME 2
include/dt-bindings/pinctrl/at91.h:#define ATMEL_PIO_DRVSTR_HI 3
But the definition if generic drive strength is actually in mA.
I think it is OK to deviate from stating it in mA, but you should
write this in the DT bindings so people do not get confused.
> @@ -814,6 +834,19 @@ static void atmel_conf_pin_config_dbg_show(struct pinctrl_dev *pctldev,
> seq_printf(s, "%s ", "open-drain");
> if (conf & ATMEL_PIO_SCHMITT_MASK)
> seq_printf(s, "%s ", "schmitt");
> + if (conf & ATMEL_PIO_DRVSTR_MASK) {
> + switch ((conf & ATMEL_PIO_DRVSTR_MASK) >> ATMEL_PIO_DRVSTR_OFFSET) {
> + case ATMEL_PIO_DRVSTR_LO:
> + seq_printf(s, "%s ", "low-drive");
> + break;
> + case ATMEL_PIO_DRVSTR_ME:
> + seq_printf(s, "%s ", "medium-drive");
> + break;
> + case ATMEL_PIO_DRVSTR_HI:
> + seq_printf(s, "%s ", "high-drive");
> + break;
But here you know what VDDIOP is, right?
So in debugfs you could actually print the real drive strength
in mA, or both "medium-drive, %u mA"?
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-01-22 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 16:02 [PATCH] pinctrl: at91-pio4: add support for drive-strength property Ludovic Desroches
2018-01-22 8:37 ` Linus Walleij [this message]
[not found] ` <CACRpkdanweSmHd_M+feHauEHtvKSW+-W=djb186BFdbxTf20Jg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-22 17:05 ` Ludovic Desroches
2018-01-29 19:01 ` Rob Herring
2018-02-01 9:50 ` Ludovic Desroches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACRpkdanweSmHd_M+feHauEHtvKSW+-W=djb186BFdbxTf20Jg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).