From: "Heiko Stübner" <heiko@sntech.de>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Brian Norris <briannorris@chromium.org>
Subject: Re: [PATCH 2/2] ARM: dts: rockchip: Configure BT_HOST_WAKE as wake-up signal on veyron
Date: Wed, 05 Jun 2019 23:11:12 +0200 [thread overview]
Message-ID: <3079472.D8Re4Zsj2W@diego> (raw)
In-Reply-To: <20190605204320.22343-2-mka@chromium.org>
Am Mittwoch, 5. Juni 2019, 22:43:20 CEST schrieb Matthias Kaehlcke:
> This enables wake up on Bluetooth activity when the device is
> suspended. The BT_HOST_WAKE signal is only connected on devices
> with BT module that are connected through UART.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
Housekeeping question, with the two Signed-off-by lines, is Doug the
original author, or was this Co-developer-by?
Heiko
> ---
> arch/arm/boot/dts/rk3288-veyron.dtsi | 29 ++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/arch/arm/boot/dts/rk3288-veyron.dtsi b/arch/arm/boot/dts/rk3288-veyron.dtsi
> index cc4c3595f145..145cac7c0847 100644
> --- a/arch/arm/boot/dts/rk3288-veyron.dtsi
> +++ b/arch/arm/boot/dts/rk3288-veyron.dtsi
> @@ -23,6 +23,31 @@
> reg = <0x0 0x0 0x0 0x80000000>;
> };
>
> + bt_activity: bt-activity {
> + compatible = "gpio-keys";
> + pinctrl-names = "default";
> + pinctrl-0 = <&bt_host_wake>;
> +
> + /*
> + * HACK: until we have an LPM driver, we'll use an
> + * ugly GPIO key to allow Bluetooth to wake from S3.
> + * This is expected to only be used by BT modules that
> + * use UART for comms. For BT modules that talk over
> + * SDIO we should use a wakeup mechanism related to SDIO.
> + *
> + * Use KEY_RESERVED here since that will work as a wakeup but
> + * doesn't get reported to higher levels (so doesn't confuse
> + * Chrome).
> + */
> + bt-wake {
> + label = "BT Wakeup";
> + gpios = <&gpio4 RK_PD7 GPIO_ACTIVE_HIGH>;
> + linux,code = <KEY_RESERVED>;
> + wakeup-source;
> + };
> +
> + };
> +
> power_button: power-button {
> compatible = "gpio-keys";
> pinctrl-names = "default";
> @@ -555,6 +580,10 @@
> rockchip,pins = <4 RK_PD5 RK_FUNC_GPIO &pcfg_pull_none>;
> };
>
> + bt_host_wake: bt-host-wake {
> + rockchip,pins = <4 31 RK_FUNC_GPIO &pcfg_pull_down>;
> + };
> +
> /*
> * We run sdio0 at max speed; bump up drive strength.
> * We also have external pulls, so disable the internal ones.
>
next prev parent reply other threads:[~2019-06-05 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 20:43 [PATCH 1/2] ARM: dts: rockchip: Split GPIO keys for veyron into multiple devices Matthias Kaehlcke
2019-06-05 20:43 ` [PATCH 2/2] ARM: dts: rockchip: Configure BT_HOST_WAKE as wake-up signal on veyron Matthias Kaehlcke
2019-06-05 21:11 ` Heiko Stübner [this message]
2019-06-05 21:24 ` Matthias Kaehlcke
2019-06-05 21:52 ` Heiko Stübner
2019-06-06 10:46 ` Heiko Stuebner
2019-06-06 17:56 ` Matthias Kaehlcke
2019-06-06 23:34 ` Doug Anderson
2019-06-14 9:41 ` Heiko Stuebner
2019-06-06 23:32 ` Doug Anderson
2019-06-06 10:44 ` [PATCH 1/2] ARM: dts: rockchip: Split GPIO keys for veyron into multiple devices Heiko Stuebner
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=3079472.D8Re4Zsj2W@diego \
--to=heiko@sntech.de \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.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;
as well as URLs for NNTP newsgroup(s).