[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221021011125.GA2104528-robh@kernel.org>
Date: Thu, 20 Oct 2022 20:11:25 -0500
From: Rob Herring <robh@...nel.org>
To: Sai Krishna Potthuri <sai.krishna.potthuri@....com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Michal Simek <michal.simek@...inx.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
devicetree@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
saikrishna12468@...il.com, git@....com, stable@...r.kernel.org
Subject: Re: [PATCH v2 2/2] Revert "dt-bindings: pinctrl-zynqmp: Add
output-enable configuration"
On Mon, Oct 17, 2022 at 06:33:03PM +0530, Sai Krishna Potthuri wrote:
> This reverts commit 133ad0d9af99bdca90705dadd8d31c20bfc9919f.
>
> On systems with older PMUFW (Xilinx ZynqMP Platform Management Firmware)
> using these pinctrl properties can cause system hang because there is
> missing feature autodetection.
> When this feature is implemented, support for these two properties should
> bring back.
So I'm going to get to review the revert of the revert at some point?
Why do the properties need to be removed from the binding? They work on
'not older' firmware, right? Isn't just removing the driver support or
removing from .dts files enough?
Rob
Powered by blists - more mailing lists