From: Dario Binacchi <dariobin@libero.it>
To: linux-kernel@vger.kernel.org
Cc: Dario Binacchi <dariobin@libero.it>,
Tony Lindgren <tony@atomide.com>,
Drew Fustini <drew@beagleboard.org>,
Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: [PATCH v3 1/3] docs/pinctrl: update `pins' description under debugfs
Date: Thu, 20 May 2021 22:27:28 +0200 [thread overview]
Message-ID: <20210520202730.4444-2-dariobin@libero.it> (raw)
In-Reply-To: <20210520202730.4444-1-dariobin@libero.it>
Optionally the `pins' file created inside the `/sys/kernel/debug/pinctrl'
subdirectory of each pin controller device now allows you to set the
mux register of a pin.
Signed-off-by: Dario Binacchi <dariobin@libero.it>
---
(no changes since v1)
Documentation/driver-api/pin-control.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/driver-api/pin-control.rst b/Documentation/driver-api/pin-control.rst
index e2474425fb0c..3d8192fa45a3 100644
--- a/Documentation/driver-api/pin-control.rst
+++ b/Documentation/driver-api/pin-control.rst
@@ -1447,6 +1447,9 @@ controller device containing these files:
- ``pins``: prints a line for each pin registered on the pin controller. The
pinctrl driver may add additional information such as register contents.
+ Optionally writes the mux register for the selected pin.
+ e.g. to write the value 0x73 in the mux register of pin 19:
+ echo 19 0x73 >/sys/kernel/debug/pinctrl/pins
- ``gpio-ranges``: print ranges that map gpio lines to pins on the controller
--
2.17.1
next prev parent reply other threads:[~2021-05-20 20:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 20:27 [PATCH v3 0/3] am335x: set pinmux registers from pins debug file Dario Binacchi
2021-05-20 20:27 ` Dario Binacchi
2021-05-20 20:27 ` Dario Binacchi [this message]
2021-05-20 20:27 ` [PATCH v3 2/3] pinctrl: core: configure pinmux " Dario Binacchi
2021-05-21 6:44 ` Vladimir Zapolskiy
2021-05-24 17:28 ` Dario Binacchi
2021-05-24 18:52 ` Vladimir Zapolskiy
2021-05-25 5:15 ` Tony Lindgren
2021-05-27 19:23 ` Dario Binacchi
2021-05-27 19:57 ` Vladimir Zapolskiy
2021-05-27 20:33 ` Dario Binacchi
2021-05-28 8:34 ` Vladimir Zapolskiy
2021-05-28 9:07 ` Linus Walleij
2021-06-02 5:03 ` Tony Lindgren
2021-06-11 8:29 ` Dario Binacchi
2021-05-20 20:27 ` [PATCH v3 3/3] pinctrl: single: set " Dario Binacchi
2021-05-20 20:27 ` Dario Binacchi
2021-05-21 6:44 ` Vladimir Zapolskiy
2021-05-21 6:44 ` Vladimir Zapolskiy
2021-05-25 0:18 ` [PATCH v3 0/3] am335x: set pinmux registers " Linus Walleij
2021-05-25 0:18 ` Linus Walleij
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=20210520202730.4444-2-dariobin@libero.it \
--to=dariobin@libero.it \
--cc=andy.shevchenko@gmail.com \
--cc=corbet@lwn.net \
--cc=drew@beagleboard.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.