[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE-0n50CvqhJ5e4zXGhvABg2_CJc9QDHTU2ZiJUrwahyBLROaA@mail.gmail.com>
Date: Thu, 3 Feb 2022 21:28:35 +0000
From: Stephen Boyd <swboyd@...omium.org>
To: Bjorn Andersson <bjorn.andersson@...aro.org>,
Douglas Anderson <dianders@...omium.org>
Cc: pmaliset@...eaurora.org, mka@...omium.org,
quic_rjendra@...cinc.com,
Shaik Sajida Bhanu <sbhanu@...eaurora.org>,
kgodara@...eaurora.org, konrad.dybcio@...ainline.org,
Sankeerth Billakanti <quic_sbillaka@...cinc.com>,
sibis@...eaurora.org, Andy Gross <agross@...nel.org>,
Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 05/14] arm64: dts: qcom: sc7280-idp: No need for
"input-enable" on sw_ctrl
Quoting Douglas Anderson (2022-02-02 13:23:39)
> Specifying "input-enable" on a MSM GPIO is a no-op for the most
> part. The only thing it really does is to explicitly force the output
> of a GPIO to be disabled right at the point of a pinctrl
> transition. We don't need to do this and we don't typically specify
> "input-enable" unless there's a good reason to. Remove it.
>
> Signed-off-by: Douglas Anderson <dianders@...omium.org>
> Reviewed-by: Matthias Kaehlcke <mka@...omium.org>
> ---
Reviewed-by: Stephen Boyd <swboyd@...omium.org>
Powered by blists - more mailing lists