public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Faiz Abbas <faiz_abbas@ti.com>
To: tony@atomide.com
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	linux@armlinux.org.uk, linux-kernel@vger.kernel.org,
	robh+dt@kernel.org, bcousson@baylibre.com,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: am437x-gp-evm: Add support for buzzer
Date: Wed, 2 Aug 2017 15:00:49 +0530	[thread overview]
Message-ID: <c135a805-868a-87fc-ce78-b4e49139211d@ti.com> (raw)
In-Reply-To: <1497935361-11019-1-git-send-email-faiz_abbas@ti.com>



On Tuesday 20 June 2017 10:39 AM, Faiz Abbas wrote:
> Add support for onboard gpio buzzer. It works using
> the gpio-beeper driver. Pinmux entries for GPIO
> controlling the buzzer are also added.

Gentle ping

Regards,
Faiz
> 
> Signed-off-by: Faiz Abbas <faiz_abbas@ti.com>
> ---
>  arch/arm/boot/dts/am437x-gp-evm.dts | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/am437x-gp-evm.dts b/arch/arm/boot/dts/am437x-gp-evm.dts
> index 397e98b..24cdf6d 100644
> --- a/arch/arm/boot/dts/am437x-gp-evm.dts
> +++ b/arch/arm/boot/dts/am437x-gp-evm.dts
> @@ -149,6 +149,13 @@
>  			system-clock-frequency = <12000000>;
>  		};
>  	};
> +
> +	beeper: beeper {
> +		compatible = "gpio-beeper";
> +		pinctrl-names = "default";
> +		pinctrl-0 = <&beeper_pins>;
> +		gpios = <&gpio4 12 GPIO_ACTIVE_HIGH>;
> +	};
>  };
>  
>  &am43xx_pinmux {
> @@ -510,6 +517,13 @@
>  			AM4372_IOPAD(0x974, PIN_OUTPUT_PULLDOWN | MUX_MODE0)	/* uart0_txd.uart0_txd */
>  		>;
>  	};
> +
> +	beeper_pins: beeper_pins {
> +		pinctrl-single,pins = <
> +			AM4372_IOPAD(0x9e0, PIN_OUTPUT_PULLUP | MUX_MODE7)	/* cam1_field.gpio4_12 */
> +		>;
> +	};
> +
>  };
>  
>  &uart0 {
> 

  reply	other threads:[~2017-08-02  9:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20  5:09 [PATCH] ARM: dts: am437x-gp-evm: Add support for buzzer Faiz Abbas
2017-08-02  9:30 ` Faiz Abbas [this message]
2017-08-07  6:50   ` Tony Lindgren
2017-08-10 16:36   ` Tony Lindgren

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=c135a805-868a-87fc-ce78-b4e49139211d@ti.com \
    --to=faiz_abbas@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.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