From: Sai Krishna Potthuri <sai.krishna.potthuri@amd.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Michal Simek <michal.simek@xilinx.com>,
Rob Herring <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>
Cc: <devicetree@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<saikrishna12468@gmail.com>, <git@amd.com>,
Sai Krishna Potthuri <sai.krishna.potthuri@amd.com>
Subject: [PATCH v2 0/2] pinctrl: pinctrl-zynqmp: Revert output-enable and bias-high-impedance support
Date: Mon, 17 Oct 2022 18:33:01 +0530 [thread overview]
Message-ID: <20221017130303.21746-1-sai.krishna.potthuri@amd.com> (raw)
Having support for output-enable and bias-high-impedance properties
causing system hang with older Xilinx ZynqMP Platform Management Firmware
because there is missing autodetection feature.
When this feature is implemented, support for these two properties should
bring back.
changes in v2:
-> Added stable tree tag in 1/2 and 2/2 patches.
Sai Krishna Potthuri (2):
Revert "pinctrl: pinctrl-zynqmp: Add support for output-enable and
bias-high-impedance"
Revert "dt-bindings: pinctrl-zynqmp: Add output-enable configuration"
.../devicetree/bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml | 4 ----
drivers/pinctrl/pinctrl-zynqmp.c | 9 ---------
2 files changed, 13 deletions(-)
--
2.17.1
next reply other threads:[~2022-10-17 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 13:03 Sai Krishna Potthuri [this message]
2022-10-17 13:03 ` [PATCH v2 1/2] Revert "pinctrl: pinctrl-zynqmp: Add support for output-enable and bias-high-impedance" Sai Krishna Potthuri
2022-10-17 13:03 ` [PATCH v2 2/2] Revert "dt-bindings: pinctrl-zynqmp: Add output-enable configuration" Sai Krishna Potthuri
2022-10-21 1:11 ` Rob Herring
2022-10-21 7:21 ` Michal Simek
2022-10-17 13:13 ` [PATCH v2 0/2] pinctrl: pinctrl-zynqmp: Revert output-enable and bias-high-impedance support Michal Simek
2022-10-18 7:51 ` Linus Walleij
2022-10-18 8:06 ` Michal Simek
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=20221017130303.21746-1-sai.krishna.potthuri@amd.com \
--to=sai.krishna.potthuri@amd.com \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=saikrishna12468@gmail.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).