| Message ID | 20240102140734.v4.8.Idc995ce08a52ba4c5fde0685118ddf2873fc8acd@changeid |
|---|---|
| State | New |
| Headers |
Return-Path: <linux-kernel+bounces-14832-ouuuleilei=gmail.com@vger.kernel.org>
Delivered-To: ouuuleilei@gmail.com
Received: by 2002:a05:7301:6f82:b0:100:9c79:88ff with SMTP id
tb2csp4685436dyb;
Tue, 2 Jan 2024 13:11:48 -0800 (PST)
X-Google-Smtp-Source:
AGHT+IHtik3WaUuW2L+jVKHk1KcRp69pqfowW8wnxSBFOGAvGX9ciHWcUdSW5UO5FWtbzKxZ/Bw7
X-Received: by 2002:a37:ac0b:0:b0:781:8b48:f2b3 with SMTP id
e11-20020a37ac0b000000b007818b48f2b3mr7622192qkm.101.1704229907799;
Tue, 02 Jan 2024 13:11:47 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1704229907; cv=none;
d=google.com; s=arc-20160816;
b=oNrehkksQOTcmTj8zGiefnVmByojRDxDfs7CIHpY6EjP9OzuNKfKHJu5YIvlVpmmU9
kdKUfINUlcURCqcfEjtb9RfX61+MRmwedfegvinoSqG87TMTlL//sH77xRb/oFTnUddZ
I0kUr5GY1vV32sKxUnclqNTj2yF0RRwmLjrTrvvjI67/0OfMrA7OzFAAu5EpN90pRbhy
NlHo5RlUG0G7xInQ0jpQcXj4S6i6+5z6M+p44wyXBz69ZJ8PLmQK6eNS0D/o1wGtyUJp
A4/kcDwV9qx5HPrasnPTEJ348w7ldyq208O22os/90PUqBvODXvnQklsQc0jlZLLLmch
yT2w==
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=Iih8S9CbSKYXK6Eu1V5z5fk9f7rCImQ6DnJQzgwRsXQ=;
fh=8uK+O3dmXFXwuw+YdqmYBWrpgbsbP+F5u0lzNXYrRuM=;
b=ybBONFBy2XLJMAWSlRRcHk15fymA3kxzcplONcyrjRoOhRCxivIuF/BDiGd930Vgq/
dgtJ/Q2tp9UlIcf11SvoFefJK0L9hL6u/jXRGw4oe27f1d6uq6GQQufV+Vnd4+lB2Dew
Q/SKx/8vvCkc08wDAGTxb5oSPqCA7haRcTojQfHgJTfkchFsVVyODpJEjDYsmdQ/KyZ2
vm2aUE478TFeYql+LklnFXatVAIoo82NA565QMioy3+MN6jWc8ImqLWcN3oR4E2oGM0E
TlW4KGNSAXHMTx+YenrVOQZzr66UI7cO8yyQvYbA+FKVJYjBDumX1tNabbtjozCkG5k5
6aAQ==
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass header.i=@chromium.org header.s=google header.b=NxKC8Bg1;
spf=pass (google.com: domain of
linux-kernel+bounces-14832-ouuuleilei=gmail.com@vger.kernel.org designates
147.75.199.223 as permitted sender)
smtp.mailfrom="linux-kernel+bounces-14832-ouuuleilei=gmail.com@vger.kernel.org";
dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org
Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [147.75.199.223])
by mx.google.com with ESMTPS id
s18-20020a05620a255200b007817232fbf1si12532252qko.161.2024.01.02.13.11.47
for <ouuuleilei@gmail.com>
(version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
Tue, 02 Jan 2024 13:11:47 -0800 (PST)
Received-SPF: pass (google.com: domain of
linux-kernel+bounces-14832-ouuuleilei=gmail.com@vger.kernel.org designates
147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Authentication-Results: mx.google.com;
dkim=pass header.i=@chromium.org header.s=google header.b=NxKC8Bg1;
spf=pass (google.com: domain of
linux-kernel+bounces-14832-ouuuleilei=gmail.com@vger.kernel.org designates
147.75.199.223 as permitted sender)
smtp.mailfrom="linux-kernel+bounces-14832-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 ny.mirrors.kernel.org (Postfix) with ESMTPS id 9607E1C229AB
for <ouuuleilei@gmail.com>; Tue, 2 Jan 2024 21:11:47 +0000 (UTC)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
by smtp.subspace.kernel.org (Postfix) with ESMTP id A234518640;
Tue, 2 Jan 2024 21:08:55 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org;
dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org
header.b="NxKC8Bg1"
X-Original-To: linux-kernel@vger.kernel.org
Received: from mail-io1-f44.google.com (mail-io1-f44.google.com
[209.85.166.44])
(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 926811799E
for <linux-kernel@vger.kernel.org>; Tue, 2 Jan 2024 21:08:51 +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-f44.google.com with SMTP id
ca18e2360f4ac-7ba7c845e1aso589483239f.2
for <linux-kernel@vger.kernel.org>;
Tue, 02 Jan 2024 13:08:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=chromium.org; s=google; t=1704229730; x=1704834530;
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=Iih8S9CbSKYXK6Eu1V5z5fk9f7rCImQ6DnJQzgwRsXQ=;
b=NxKC8Bg1E9loB28npLQy86G1Uk0jberzz0pipqr7NQKvJ55wAfFyIo/RUlTOuhxG8u
jQOtXZm8zekL6yMFVXzNdqAqdEDBIxF65VbIf9DGIXLYs5Dz0n1Qr4cPnF3jb3NqdZ55
Sb4E+K1G9ILQM6kDWcB0LKl5Ru1vymvI/M29o=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1704229730; x=1704834530;
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=Iih8S9CbSKYXK6Eu1V5z5fk9f7rCImQ6DnJQzgwRsXQ=;
b=TQsTheEMRdgQA1yoHkLsDD91tr/ac9ieESB8vEd2zhjINGvzw8CnrOsd/Oshplcw6T
7MbtJuEXLbGTCJbvAVUwFOw033x8MMawZpRRy8JjbYdFQp1T5i5Zw0LaaYnGInPWLiUF
JBTjmpHRIlqLj85RZfFzu2Yj7uKl4G3ZptVUfqB9mJ99JoTnP3223L7M7yV6TBGRwFe2
ujS7aHeWeCLY68DXV/X+ladL6RHuQXYmDss5UZGsaaxN6GsDgDtFACsuNhrtv1BiEK12
MTrkFAdfHRxEy/AqOu+mUMrwVCXM+h5dl2zBVo6urzEk6qetXHRHQLxx4DsfDpFN1ojQ
DDdA==
X-Gm-Message-State: AOJu0YyHjN36aGh0QztxAu+eKtfEGpye17jDLzMJdeMV5I5PyDHXUtzx
xwyf1j3nbuKrc5tNCXhcEby4080Ey1UbdNgbnAQhkDQr8M4J
X-Received: by 2002:a5e:a50b:0:b0:7b7:55fc:7d4 with SMTP id
11-20020a5ea50b000000b007b755fc07d4mr24457360iog.18.1704229730619;
Tue, 02 Jan 2024 13:08:50 -0800 (PST)
Received: from markhas1.lan (71-218-50-136.hlrn.qwest.net. [71.218.50.136])
by smtp.gmail.com with ESMTPSA id
bo18-20020a056638439200b0046993034c91sm6956978jab.77.2024.01.02.13.08.49
(version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
Tue, 02 Jan 2024 13:08:50 -0800 (PST)
From: Mark Hasemeyer <markhas@chromium.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>,
Rob Herring <robh@kernel.org>,
Andy Shevchenko <andriy.shevchenko@intel.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Raul Rangel <rrangel@chromium.org>,
Tzung-Bi Shih <tzungbi@kernel.org>,
Mark Hasemeyer <markhas@chromium.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: [PATCH v4 08/24] ARM: dts: samsung: exynos5800: Enable cros-ec-spi as
wake source
Date: Tue, 2 Jan 2024 14:07:32 -0700
Message-ID:
<20240102140734.v4.8.Idc995ce08a52ba4c5fde0685118ddf2873fc8acd@changeid>
X-Mailer: git-send-email 2.43.0.472.g3155946c3a-goog
In-Reply-To: <20240102210820.2604667-1-markhas@chromium.org>
References: <20240102210820.2604667-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: 1787014579493601882
X-GMAIL-MSGID: 1787014579493601882
|
| Series |
Improve IRQ wake capability reporting and update the cros_ec driver to use it
|
|
Commit Message
Mark Hasemeyer
Jan. 2, 2024, 9:07 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.
Signed-off-by: Mark Hasemeyer <markhas@chromium.org>
---
(no changes since v3)
Changes in v3:
-Update commit message to provide details of the motivation behind the
change
Changes in v2:
-Split by arch/soc
arch/arm/boot/dts/samsung/exynos5800-peach-pi.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/samsung/exynos5800-peach-pi.dts b/arch/arm/boot/dts/samsung/exynos5800-peach-pi.dts index f91bc4ae008e4..9bbbdce9103a6 100644 --- a/arch/arm/boot/dts/samsung/exynos5800-peach-pi.dts +++ b/arch/arm/boot/dts/samsung/exynos5800-peach-pi.dts @@ -949,6 +949,7 @@ cros_ec: cros-ec@0 { reg = <0>; spi-max-frequency = <3125000>; google,has-vbc-nvram; + wakeup-source; controller-data { samsung,spi-feedback-delay = <1>;