From: mark.roszko@gmail.com (Marek Roszko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] pinctrl: at91: update documentation for drive strength options and tweaks
Date: Sat, 23 Aug 2014 23:12:06 -0400 [thread overview]
Message-ID: <1408849926-9603-3-git-send-email-mark.roszko@gmail.com> (raw)
In-Reply-To: <1408849926-9603-1-git-send-email-mark.roszko@gmail.com>
The drive strength patched introduced the atmel,sama5d-pinctrl compatible string.
Drive strength is now an option for the CONFIG bits per pin. Also added note about
MULTIDRIVE being equivalent to open-drain output and added missing "s" at the
end of need everywhere in the bits descriptions.
Signed-off-by: Marek Roszko <mark.roszko@gmail.com>
---
.../bindings/pinctrl/atmel,at91-pinctrl.txt | 22 +++++++++++++++-------
1 file changed, 15 insertions(+), 7 deletions(-)
diff --git a/Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt
index 02ab5ab..b7a93e8 100644
--- a/Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt
+++ b/Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt
@@ -19,6 +19,7 @@ such as pull-up, multi drive, etc.
Required properties for iomux controller:
- compatible: "atmel,at91rm9200-pinctrl" or "atmel,at91sam9x5-pinctrl"
+ or "atmel,sama5d3-pinctrl"
- atmel,mux-mask: array of mask (periph per bank) to describe if a pin can be
configured in this periph mode. All the periph and bank need to be describe.
@@ -85,13 +86,20 @@ Required properties for pin configuration node:
PIN_BANK 0 is pioA, PIN_BANK 1 is pioB...
Bits used for CONFIG:
-PULL_UP (1 << 0): indicate this pin need a pull up.
-MULTIDRIVE (1 << 1): indicate this pin need to be configured as multidrive.
-DEGLITCH (1 << 2): indicate this pin need deglitch.
-PULL_DOWN (1 << 3): indicate this pin need a pull down.
-DIS_SCHMIT (1 << 4): indicate this pin need to disable schmit trigger.
-DEBOUNCE (1 << 16): indicate this pin need debounce.
-DEBOUNCE_VAL (0x3fff << 17): debounce val.
+PULL_UP (1 << 0): indicate this pin needs a pull up.
+MULTIDRIVE (1 << 1): indicate this pin needs to be configured as multi-drive.
+ Multi-drive is equivalent to open-drain type output.
+DEGLITCH (1 << 2): indicate this pin needs deglitch.
+PULL_DOWN (1 << 3): indicate this pin needs a pull down.
+DIS_SCHMIT (1 << 4): indicate this pin needs to the disable schmitt trigger.
+DRIVE_STRENGTH (3 << 5): indicate the drive strength of the pin using the
+ following values:
+ 00 - No change (reset state value kept)
+ 01 - Low
+ 10 - Medium
+ 11 - High
+DEBOUNCE (1 << 16): indicate this pin needs debounce.
+DEBOUNCE_VAL (0x3fff << 17): debounce value.
NOTE:
Some requirements for using atmel,at91rm9200-pinctrl binding:
--
1.9.1
next prev parent reply other threads:[~2014-08-24 3:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-24 3:12 [PATCH v2 1/3] pinctrl: at91: add drive strength configuration Marek Roszko
2014-08-24 3:12 ` [PATCH v2 2/3] ARM: at91/dt: at91: use new pinctrl id for sama5 Marek Roszko
2014-09-05 7:34 ` Linus Walleij
2014-09-08 8:07 ` Nicolas Ferre
2014-09-18 15:32 ` Nicolas Ferre
2014-08-24 3:12 ` Marek Roszko [this message]
2014-09-05 7:36 ` [PATCH v2 3/3] pinctrl: at91: update documentation for drive strength options and tweaks Linus Walleij
2014-09-01 8:27 ` [PATCH v2 1/3] pinctrl: at91: add drive strength configuration Linus Walleij
2014-09-01 8:28 ` Jean-Christophe PLAGNIOL-VILLARD
2014-09-05 7:33 ` Linus Walleij
2014-09-05 7:56 ` Nicolas Ferre
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=1408849926-9603-3-git-send-email-mark.roszko@gmail.com \
--to=mark.roszko@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).