Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 81DD2C433F5 for ; Tue, 11 Jan 2022 20:19:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345653AbiAKUTX (ORCPT ); Tue, 11 Jan 2022 15:19:23 -0500 Received: from smtp-relay-internal-1.canonical.com ([185.125.188.123]:38580 "EHLO smtp-relay-internal-1.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1346616AbiAKUSf (ORCPT ); Tue, 11 Jan 2022 15:18:35 -0500 Received: from mail-ed1-f69.google.com (mail-ed1-f69.google.com [209.85.208.69]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-1.canonical.com (Postfix) with ESMTPS id 9678640054 for ; Tue, 11 Jan 2022 20:18:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1641932314; bh=JHHUBFr6OMR8zM8/i6cAvf5NoFmGRGJHrNiT4tfy3rM=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=QYJrHOKKSlB3cbXm8e5jcJ3GBAYGUW/pUId7h6rBwulI8uH80CQkkqYJMzUPN/cSu NWBetcJl0WlsIJFwiEbmkW6/IpxfflQPUiLQpAhY1Zkg9BHFE24eFrXSz1gvTUguEF K2Z3FZ8v/wmgf1DSH5lvG7aLr8AxemABlxRyDcmQpAXJgpCtvLJSBjuHnlABT53zs7 UZELhrBNhWw2Uc5Knp4ukn3heqVR5qvgZQBIV/tUhiOkZYpNtmQnocUlv2iVZSqs1d MWA6qxAjgMiflLOYnrAiKDNphNvpI5zX0RKZqHRc7yLTX4xybz3Ye/DnjVjCcITMWd pnDD1MbRTsijw== Received: by mail-ed1-f69.google.com with SMTP id eg24-20020a056402289800b003fe7f91df01so206369edb.6 for ; Tue, 11 Jan 2022 12:18:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=JHHUBFr6OMR8zM8/i6cAvf5NoFmGRGJHrNiT4tfy3rM=; b=M17yv+DjnimWDM7568U8ykIVy+WtXtsV7KU51FuaCkMU93cdyPr1n5VaqL+usLTWZj IMILmLYTnstVMi/W7RNftejqt5phO9dtPgQCO3J0DHXbkpwH09H+llk6N3UOIODEZov6 wKif6961jyfqUhSNx1NwIylSEqhuUJH2ZVoQNCZiYAvQuxyu3iEiGZjFIBtjtvgfMLTh NixrOiz5lsvMBpIQELTypnrZA+Z4b8j940wiraoFzUSc9jdRJ07XnmtfXC4HTo91Ipzi YauTbzePVt158wsEJq6EGHQ+hVlmY+KyPuMSdPPGXo+IXT4I8CHQo582mI4WbjwvMp6g JR5Q== X-Gm-Message-State: AOAM530/Q0UkEluYy2bvHlyaTkXUTj9SeCc4UvsYwhDlDCebFex1ykAu sXY3HgqAsu43nu+zj6YTZ3sbxaWX5o1CTnKS/VgNlv6+a9QgJW9i8OcZYKcO2j3jMlnh8G/GRuR dXHKmRkIcRlXaT2hFEpBrkrea7np9pXQaEEBePvAUKA== X-Received: by 2002:a17:907:9712:: with SMTP id jg18mr5265430ejc.328.1641932310995; Tue, 11 Jan 2022 12:18:30 -0800 (PST) X-Google-Smtp-Source: ABdhPJxy9/rcIjTsKZFScympQBOQBEOBe9i4BBbC40lJsXnfYnnYR9RgCbIQ5WcOvNKS259ya4jL8g== X-Received: by 2002:a17:907:9712:: with SMTP id jg18mr5265420ejc.328.1641932310844; Tue, 11 Jan 2022 12:18:30 -0800 (PST) Received: from localhost.localdomain (xdsl-188-155-168-84.adslplus.ch. [188.155.168.84]) by smtp.gmail.com with ESMTPSA id e4sm4030881ejs.13.2022.01.11.12.18.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Jan 2022 12:18:30 -0800 (PST) From: Krzysztof Kozlowski To: Tomasz Figa , Krzysztof Kozlowski , Sylwester Nawrocki , Linus Walleij , Rob Herring , linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Marek Szyprowski , Sam Protsenko , Chanho Park , Alim Akhtar Subject: [PATCH v2 27/28] arm64: dts: exynos: use dedicated wake-up pinctrl compatible in Exynos850 Date: Tue, 11 Jan 2022 21:17:21 +0100 Message-Id: <20220111201722.327219-21-krzysztof.kozlowski@canonical.com> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20220111201426.326777-1-krzysztof.kozlowski@canonical.com> References: <20220111201426.326777-1-krzysztof.kozlowski@canonical.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Older Samsung Exynos SoC pin controller nodes (Exynos3250, Exynos4, Exynos5, Exynos5433) with external wake-up interrupts, expected to have one interrupt for multiplexing these wake-up interrupts. Also they expected to have exactly one pin controller capable of external wake-up interrupts. It seems however that newer ARMv8 Exynos SoC like Exynos850 and ExynosAutov9 have differences: 1. No multiplexed external wake-up interrupt, only direct, 2. More than one pin controller capable of external wake-up interrupts. Use dedicated Exynos850 compatible for its external wake-up interrupts controller to indicate the differences. Signed-off-by: Krzysztof Kozlowski --- arch/arm64/boot/dts/exynos/exynos850.dtsi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/arm64/boot/dts/exynos/exynos850.dtsi b/arch/arm64/boot/dts/exynos/exynos850.dtsi index 4f0a40de5e67..bcae772e8d91 100644 --- a/arch/arm64/boot/dts/exynos/exynos850.dtsi +++ b/arch/arm64/boot/dts/exynos/exynos850.dtsi @@ -346,7 +346,7 @@ pinctrl_alive: pinctrl@11850000 { reg = <0x11850000 0x1000>; wakeup-interrupt-controller { - compatible = "samsung,exynos7-wakeup-eint"; + compatible = "samsung,exynos850-wakeup-eint"; }; }; @@ -355,7 +355,7 @@ pinctrl_cmgp: pinctrl@11c30000 { reg = <0x11c30000 0x1000>; wakeup-interrupt-controller { - compatible = "samsung,exynos7-wakeup-eint"; + compatible = "samsung,exynos850-wakeup-eint"; }; }; -- 2.32.0