devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Fabien Dessenne <fabien.dessenne@foss.st.com>,
	Rob Herring <robh+dt@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	<devicetree@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] ARM: dts: stm32: add UserPA13 button on stm32mp135f-dk
Date: Tue, 3 May 2022 15:49:25 +0200	[thread overview]
Message-ID: <4cb68dce-b334-627f-d45d-62b9a10dab6c@foss.st.com> (raw)
In-Reply-To: <20220503094133.502487-1-fabien.dessenne@foss.st.com>

On 5/3/22 11:41, Fabien Dessenne wrote:
> The PA13 user button is connected to the PA13 pin of the stm32mp135f-dk
> board. It requires an internal pull-up configuration.
> 
> Signed-off-by: Fabien Dessenne <fabien.dessenne@foss.st.com>
> ---
>   arch/arm/boot/dts/stm32mp135f-dk.dts | 11 +++++++++++
>   1 file changed, 11 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/stm32mp135f-dk.dts b/arch/arm/boot/dts/stm32mp135f-dk.dts
> index 65acee0f68b7..09d6226d598f 100644
> --- a/arch/arm/boot/dts/stm32mp135f-dk.dts
> +++ b/arch/arm/boot/dts/stm32mp135f-dk.dts
> @@ -7,6 +7,7 @@
>   /dts-v1/;
>   
>   #include <dt-bindings/gpio/gpio.h>
> +#include <dt-bindings/input/input.h>
>   #include <dt-bindings/leds/common.h>
>   #include "stm32mp135.dtsi"
>   #include "stm32mp13xf.dtsi"
> @@ -25,6 +26,16 @@ memory@c0000000 {
>   		reg = <0xc0000000 0x20000000>;
>   	};
>   
> +	gpio-keys {
> +		compatible = "gpio-keys";
> +
> +		user-pa13 {
> +			label = "User-PA13";
> +			linux,code = <BTN_1>;
> +			gpios = <&gpioa 13 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>;
> +		};
> +	};
> +
>   	leds {
>   		compatible = "gpio-leds";
>   
Applied on stm32-next.

Thanks.
Alex

      reply	other threads:[~2022-05-03 13:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03  9:41 [PATCH 2/2] ARM: dts: stm32: add UserPA13 button on stm32mp135f-dk Fabien Dessenne
2022-05-03 13:49 ` Alexandre TORGUE [this message]

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=4cb68dce-b334-627f-d45d-62b9a10dab6c@foss.st.com \
    --to=alexandre.torgue@foss.st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabien.dessenne@foss.st.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).