From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,T_DKIMWL_WL_HIGH,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AE35BC28CC5 for ; Wed, 5 Jun 2019 21:11:30 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 713232075B for ; Wed, 5 Jun 2019 21:11:30 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="oNkeUTCP" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 713232075B Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=sntech.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Date:Subject:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=J7QinmAu5YbdLx26sNyX275o0wdOQiUpA0FT57+ab/M=; b=oNkeUTCPBBmAG5 6gRaGS9r4OMOu+ybD1mRf1JcWI/B5c60GD+fuHYC66xFgwl+dfZS96alPEOg6GQE8R2xbODUeRPQn SyIa0FBd/4qqTCL4xHciKACSKVCs9P/D3DGt7zuLzq2cI/X9ENeGeRYqiiFPKcbHljktQznu1IL66 9hxulVlHCEOKnhnKrlkz/HmRIXkjwv2e6IldFBq36gPWmaBiMY+wnLueohasVLBlGgfix3HBUf0WH kxtSQUxa91Ixhosu4z8/OTES3/XIBIBwCJLe0OQvbcZlKYaO4qJ3jqnYfGuKFaav04JuHOyEXNIyi QcalYX5YQitheM4KLnOw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hYdBs-0004rZ-GE; Wed, 05 Jun 2019 21:11:24 +0000 Received: from gloria.sntech.de ([185.11.138.130]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hYdBo-0004qc-JV; Wed, 05 Jun 2019 21:11:22 +0000 Received: from ip5f5a6320.dynamic.kabel-deutschland.de ([95.90.99.32] helo=diego.localnet) by gloria.sntech.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hYdBh-0000gP-2F; Wed, 05 Jun 2019 23:11:13 +0200 From: Heiko =?ISO-8859-1?Q?St=FCbner?= To: Matthias Kaehlcke 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 Message-ID: <3079472.D8Re4Zsj2W@diego> In-Reply-To: <20190605204320.22343-2-mka@chromium.org> References: <20190605204320.22343-1-mka@chromium.org> <20190605204320.22343-2-mka@chromium.org> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190605_141120_788864_8D64F0C8 X-CRM114-Status: GOOD ( 18.72 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , devicetree@vger.kernel.org, Brian Norris , linux-kernel@vger.kernel.org, Douglas Anderson , linux-rockchip@lists.infradead.org, Rob Herring , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.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 > Signed-off-by: Matthias Kaehlcke 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 = ; > + 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. > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel