From: Fabio Estevam <festevam@gmail.com>
To: linus.walleij@linaro.org
Cc: robh+dt@kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, sandor.yu@nxp.com,
Fabio Estevam <festevam@gmail.com>
Subject: [PATCH 1/2] dt-bindings: gpio: 74x164: Introduce the 'registers-default' property
Date: Wed, 30 Dec 2020 12:41:06 -0300 [thread overview]
Message-ID: <20201230154107.4151-1-festevam@gmail.com> (raw)
There are cases where a certain default output value in the 74x164
output is needed.
For example: the imx6ul-evk board has the Ethernet PHY reset controlled
by the 74x164 chip.
After enabling the OE pin, the output pins of the 74x164 chip go to
zero by default, which makes the Ethernet PHY not to be detected.
Add a new optional property called 'registers-default' that allows
describing the default output value for each shift register.
Signed-off-by: Fabio Estevam <festevam@gmail.com>
---
Documentation/devicetree/bindings/gpio/gpio-74x164.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/gpio/gpio-74x164.txt b/Documentation/devicetree/bindings/gpio/gpio-74x164.txt
index 2a97553d8d76..bf8f45896018 100644
--- a/Documentation/devicetree/bindings/gpio/gpio-74x164.txt
+++ b/Documentation/devicetree/bindings/gpio/gpio-74x164.txt
@@ -14,6 +14,8 @@ Required properties:
Optional properties:
- enable-gpios: GPIO connected to the OE (Output Enable) pin.
+- registers-default: An array of 8-bit values describing the default output
+value of each shift registers.
Example:
@@ -24,4 +26,5 @@ gpio5: gpio5@0 {
#gpio-cells = <2>;
registers-number = <4>;
spi-max-frequency = <100000>;
+ registers-default = /bits/ 8 <0x57 0xF0 0xFF 0xF0>;
};
--
2.17.1
next reply other threads:[~2020-12-30 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 15:41 Fabio Estevam [this message]
2020-12-30 15:41 ` [PATCH 2/2] gpio: 74x164: Introduce the 'registers-default' property Fabio Estevam
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=20201230154107.4151-1-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sandor.yu@nxp.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).