Message ID | 20231226122113.v3.17.Ice617703aded22ad4c806459129e1ae693eb57af@changeid |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel+bounces-11645-ouuuleilei=gmail.com@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:7301:6f82:b0:100:9c79:88ff with SMTP id tb2csp1057175dyb; Tue, 26 Dec 2023 11:27:01 -0800 (PST) X-Google-Smtp-Source: AGHT+IEUvbuHaIiPHrhfzWdWqEeZ/1qE9zAe1JdWHIJd5oAp6wZTBOssmsAHis2EK/OEmmwhAua6 X-Received: by 2002:a2e:98d5:0:b0:2cc:5fa0:69da with SMTP id s21-20020a2e98d5000000b002cc5fa069damr2795183ljj.51.1703618820867; Tue, 26 Dec 2023 11:27:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1703618820; cv=none; d=google.com; s=arc-20160816; b=KinLj2f/UUG3CoXzZlF2pckyegLs4Qm4tdSbT5CFvlPihRd7GQCaZdlO3k0hPcCEFw u3IwbJkA/WM8i9ajm8URcfgZVVzrUk/MFSjSNwLgvX9mg6xumWk6vjlK6PYnYlSB2yxN /Hf+pIeT8joDw7vILhe98OqArKmaV/K+fm0rvFlMTABTGc4a56kENvcVo6usdLkinS9k Yt/7jLBwFD//sCmFjFNPOL5sn1xkm6GBll0WV6d70KSIlznv2gA1NRkcE+5zbfQzkf0A 2ilSvhJtKor6A3z22dpzkoAmrWZs7M+YCw5xbM8cnHs+CX4Epa0/luhgrd0rAS7QAhjZ io/Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:in-reply-to:message-id :date:subject:cc:to:from:dkim-signature; bh=JesGzUfVYG0N52lEpA2lp9jd0GztoHz5e+Bd1oSHbfw=; fh=jjDxkSiPWhqNGQNnqCS2K9AU9079eaMS2Hf+qCftwT0=; b=styOb00qxPnC4S9xes1mT5WA754L6WwibNya6st5PTfSKpVPYwysjqc2JOiWzhO4LF 6vCmqKElcOGxF9AQIbmcPNX3nkuo61J9nPbhCN30AJdQnjNyca8+kVuZEV6qwVPts/6n natVzk2iQsLMllo/GdRZ4pWUjqRPxOg5gL7H4EfKCbxEw/dCINK5wlIs7XFSTbYOM3Tk 6is2BSTQcBa7sKEcAUIPoh2eQ75XEjYZ6InAVlvdqK169TbqFz2y/7qNvZjyoEoW9ddO PUExqPUlAbAbcf7xEcLP3e/LYnBWw4kZnORhatIM079KUHc5JYcAWc7xh7NPUSLsp+Y3 EY1Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=Tdy72+mN; spf=pass (google.com: domain of linux-kernel+bounces-11645-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-kernel+bounces-11645-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: from am.mirrors.kernel.org (am.mirrors.kernel.org. [2604:1380:4601:e00::3]) by mx.google.com with ESMTPS id c69-20020a509fcb000000b00554f702305fsi1528506edf.163.2023.12.26.11.27.00 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 26 Dec 2023 11:27:00 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-11645-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=Tdy72+mN; spf=pass (google.com: domain of linux-kernel+bounces-11645-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-kernel+bounces-11645-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by am.mirrors.kernel.org (Postfix) with ESMTPS id 7792E1F22A87 for <ouuuleilei@gmail.com>; Tue, 26 Dec 2023 19:27:00 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id AF42719BD3; Tue, 26 Dec 2023 19:22:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="Tdy72+mN" X-Original-To: linux-kernel@vger.kernel.org Received: from mail-io1-f43.google.com (mail-io1-f43.google.com [209.85.166.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CF37C1862D for <linux-kernel@vger.kernel.org>; Tue, 26 Dec 2023 19:22:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=chromium.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=chromium.org Received: by mail-io1-f43.google.com with SMTP id ca18e2360f4ac-7bb0ab8e79fso5334739f.1 for <linux-kernel@vger.kernel.org>; Tue, 26 Dec 2023 11:22:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; t=1703618537; x=1704223337; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=JesGzUfVYG0N52lEpA2lp9jd0GztoHz5e+Bd1oSHbfw=; b=Tdy72+mNcqjluS9WcMC1i/EDk19WIdQij/W521KpvjXHDYVvZH+U7mctE8mUgRSKLS yE0qXAtT40SP7RQwhw8zFbuW0eNyjKIia45BnsXTtsZ9SxogRwwMsB26mGQzpD5u8SvY 6JgKQU7sZ4mzWdmd0m1oxa0OrTgrfjEQYLJS4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703618537; x=1704223337; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=JesGzUfVYG0N52lEpA2lp9jd0GztoHz5e+Bd1oSHbfw=; b=w9ZA/0Xndw3t3dO65Fo7YjtRt5fkjzug1jpgO2ZgEjNjBjkM5WPOS0tasJh5s7oPXj S37rAZDQRHH/lW88/g1KG2CNd3L761UmaaEVJZulYOKAFvwNZKYq/j8jHSirxkM7/aA3 Cv45hRRTCRmTlMRjEAs71OToeDQkhfuMaBUQj86SP0UVyJu7ESVfznx4wrbay2ie1UXG vbGOuLXXrAJzZMlXZOSpWE0G24h8aD26Z4ppxvgfCzHmGUkCtOL11jxEGsCd/v8v8cOQ O8iTLpaSBsvEWJWkCoO/h+p4CVz5rBofCt/vNOl3EdKnBP/7IA6o39D8tRw5GjpWl1GT goWg== X-Gm-Message-State: AOJu0YwQHySSAK4cMtKZgbH66HU3HF4gzYi3AU35paEtLZyfLQegfJK/ NiBisDhcR5954+22qt3XVWnyJHkJVDdp/6Zpy3nbYqjXTlSW X-Received: by 2002:a5d:9718:0:b0:7ba:b7da:3cd8 with SMTP id h24-20020a5d9718000000b007bab7da3cd8mr8956064iol.17.1703618536940; Tue, 26 Dec 2023 11:22:16 -0800 (PST) Received: from markhas1.lan (71-218-50-136.hlrn.qwest.net. [71.218.50.136]) by smtp.gmail.com with ESMTPSA id gw3-20020a0566381ee300b0046b692e719esm3207609jab.150.2023.12.26.11.22.16 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 26 Dec 2023 11:22:16 -0800 (PST) From: Mark Hasemeyer <markhas@chromium.org> To: LKML <linux-kernel@vger.kernel.org> Cc: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>, Rob Herring <robh@kernel.org>, Konrad Dybcio <konrad.dybcio@linaro.org>, Sudeep Holla <sudeep.holla@arm.com>, Andy Shevchenko <andriy.shevchenko@intel.com>, Raul Rangel <rrangel@chromium.org>, Tzung-Bi Shih <tzungbi@kernel.org>, Mark Hasemeyer <markhas@chromium.org>, Conor Dooley <conor+dt@kernel.org>, Heiko Stuebner <heiko@sntech.de>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Rob Herring <robh+dt@kernel.org>, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org Subject: [PATCH v3 17/24] arm64: dts: rockchip: rk3399: Enable cros-ec-spi as wake source Date: Tue, 26 Dec 2023 12:21:21 -0700 Message-ID: <20231226122113.v3.17.Ice617703aded22ad4c806459129e1ae693eb57af@changeid> X-Mailer: git-send-email 2.43.0.472.g3155946c3a-goog In-Reply-To: <20231226192149.1830592-1-markhas@chromium.org> References: <20231226192149.1830592-1-markhas@chromium.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: <linux-kernel.vger.kernel.org> List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org> List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1786373808698243313 X-GMAIL-MSGID: 1786373808698243313 |
Series |
Improve IRQ wake capability reporting and update the cros_ec driver to use it
|
|
Commit Message
Mark Hasemeyer
Dec. 26, 2023, 7:21 p.m. UTC
The cros_ec driver currently assumes that cros-ec-spi compatible device
nodes are a wakeup-source even though the wakeup-source property is not
defined.
Some Chromebooks use a separate wake pin, while others overload the
interrupt for wake and IO. With the current assumption, spurious wakes
can occur on systems that use a separate wake pin. It is planned to
update the driver to no longer assume that the EC interrupt pin should
be enabled for wake.
Add the wakeup-source property to all cros-ec-spi compatible device
nodes to signify to the driver that they should still be a valid wakeup
source.
-Commit-changes: 3
-Update commit message to provide details of the motivation behind the
change
Signed-off-by: Mark Hasemeyer <markhas@chromium.org>
---
(no changes since v2)
Changes in v2:
-Split by arch/soc
arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi index 789fd0dcc88ba..b5734e056aef1 100644 --- a/arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi +++ b/arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi @@ -603,6 +603,7 @@ cros_ec: ec@0 { pinctrl-names = "default"; pinctrl-0 = <&ec_ap_int_l>; spi-max-frequency = <3000000>; + wakeup-source; i2c_tunnel: i2c-tunnel { compatible = "google,cros-ec-i2c-tunnel";