From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/8] arm64: dts: qcom: msm8998-sony-xperia: correct GPIO keys wakeup
Date: Sat, 4 Mar 2023 13:57:06 +0100 [thread overview]
Message-ID: <19c95fa7-d436-5171-e3bb-d466ace1fe74@linaro.org> (raw)
In-Reply-To: <20230304123358.34274-3-krzysztof.kozlowski@linaro.org>
On 4.03.2023 13:33, Krzysztof Kozlowski wrote:
> gpio-keys,wakeup is a deprecated property:
>
> msm8998-sony-xperia-yoshino-lilac.dtb: gpio-keys: button-vol-down: Unevaluated properties are not allowed ('gpio-key,wakeup' was unexpected)
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Konrad
> arch/arm64/boot/dts/qcom/msm8998-sony-xperia-yoshino.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/msm8998-sony-xperia-yoshino.dtsi b/arch/arm64/boot/dts/qcom/msm8998-sony-xperia-yoshino.dtsi
> index 820414758888..fa02e45f1c24 100644
> --- a/arch/arm64/boot/dts/qcom/msm8998-sony-xperia-yoshino.dtsi
> +++ b/arch/arm64/boot/dts/qcom/msm8998-sony-xperia-yoshino.dtsi
> @@ -106,7 +106,7 @@ button-vol-down {
> gpios = <&pm8998_gpios 5 GPIO_ACTIVE_LOW>;
> linux,input-type = <EV_KEY>;
> linux,code = <KEY_VOLUMEDOWN>;
> - gpio-key,wakeup;
> + wakeup-source;
> debounce-interval = <15>;
> };
>
> @@ -138,7 +138,7 @@ event-hall-sensor0 {
> gpios = <&tlmm 124 GPIO_ACTIVE_LOW>;
> linux,input-type = <EV_SW>;
> linux,code = <SW_LID>;
> - gpio-key,wakeup;
> + wakeup-source;
> debounce-interval = <30>;
> };
> };
next prev parent reply other threads:[~2023-03-04 12:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 12:33 [PATCH 1/8] arm64: dts: qcom: sm8150-kumano: correct GPIO keys wakeup Krzysztof Kozlowski
2023-03-04 12:33 ` [PATCH 2/8] arm64: dts: qcom: msm8998-fxtec: " Krzysztof Kozlowski
2023-03-04 12:56 ` Konrad Dybcio
2023-03-04 12:33 ` [PATCH 3/8] arm64: dts: qcom: msm8998-sony-xperia: " Krzysztof Kozlowski
2023-03-04 12:57 ` Konrad Dybcio [this message]
2023-03-04 12:33 ` [PATCH 4/8] arm64: dts: qcom: sc7280-idp: " Krzysztof Kozlowski
2023-03-04 12:57 ` Konrad Dybcio
2023-03-04 12:33 ` [PATCH 5/8] arm64: dts: qcom: sdm630-sony-xperia: " Krzysztof Kozlowski
2023-03-04 12:57 ` Konrad Dybcio
2023-03-04 12:33 ` [PATCH 6/8] arm64: dts: qcom: sm6115p-lenovo-j606f: " Krzysztof Kozlowski
2023-03-04 12:57 ` Konrad Dybcio
2023-03-04 12:33 ` [PATCH 7/8] arm64: dts: qcom: sm8250-sony-xperia: " Krzysztof Kozlowski
2023-03-04 12:57 ` Konrad Dybcio
2023-03-04 12:33 ` [PATCH 8/8] arm64: dts: qcom: sm8250-xiaomi-elish: " Krzysztof Kozlowski
2023-03-04 12:58 ` Konrad Dybcio
2023-03-04 12:56 ` [PATCH 1/8] arm64: dts: qcom: sm8150-kumano: " Konrad Dybcio
2023-03-16 3:20 ` (subset) " Bjorn Andersson
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=19c95fa7-d436-5171-e3bb-d466ace1fe74@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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