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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5AA67C433F5 for ; Tue, 11 Jan 2022 20:19:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345893AbiAKUTE (ORCPT ); Tue, 11 Jan 2022 15:19:04 -0500 Received: from smtp-relay-internal-0.canonical.com ([185.125.188.122]:60478 "EHLO smtp-relay-internal-0.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243805AbiAKUSe (ORCPT ); Tue, 11 Jan 2022 15:18:34 -0500 Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) (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-0.canonical.com (Postfix) with ESMTPS id B83E440ADA for ; Tue, 11 Jan 2022 20:18:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1641932312; bh=JHHUBFr6OMR8zM8/i6cAvf5NoFmGRGJHrNiT4tfy3rM=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=GnqFbPrNgaw1VMLR1yRa7ozMMz0YvR87CSUd0jJsr9Zt8o8z4DCxCA0x3fgAZG7I4 Rtm5LdA5TXmKvXS8E+Ww/0nicp3e/AUeb7bfcNqfF9oeG+gW60eDU9Zi+Qs8lVYfol qrW/w+s/vRQsolN20xrDC0VZwPOmtZzHeY5GxEHGrwT4MTX8M3ESTGAENjeC3JrlOS 7d/jafLZq4y0+wT7HOGg8UQakADwLFVUbKjsvUIb5kaSr7faeiXW3B5fWaq94uy6bS F2HZgHIakqezi5pwYIxO2a2tPqTPNAg20dP5NwN1gZ8j8WA1tJ99VNsPNmzDkmQZxG ibNLSKd6EyT9Q== Received: by mail-ed1-f71.google.com with SMTP id v18-20020a056402349200b003f8d3b7ee8dso146869edc.23 for ; Tue, 11 Jan 2022 12:18:32 -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=3jdNybOU4dUf67HIxfT8979mhnosJSbwKPUsZSNG3f/YxPpJi0+hpWuXuo+ypc3+6i kJItL8Ns83C9H0EixxxV8tGqybKsITrXca8qMs6idSZH4btb6/786rWM6xptHNlwfWq7 X2mtLsXaSs1oMUP8rgc39/skzrGidZAOdJno1mM4JFshdOvi6FlIhbys6VQdQdQNDi7G ziHGTjd71I4mupqey/v9OIT57FiFx25TQkO59plRmwe9PWKECMwU4dPB1LXsfeDNpZ2K YXHyBNT0B07D9cT1fcgAUm+XxeLcoCkpl7K6KfxP/ZnQRAu7Nu30E2q5CcYMq9d6E4/h EPyA== X-Gm-Message-State: AOAM531GDacSBXf/DNI3BOFvAk5mCbCWhfqqj3QC3rjZOmRocVXHbWVZ Y/nWj7zo/M2YKcK9ErWcC0CvQUGi/Go63LqsPnNCaO2/9h9/0IOeXPhw32p9dkMi8/HU0GbKWmI Cnjri7Gam9sEBPfu+YgqkDldTTzqDn6T3zEiTtsA= X-Received: by 2002:a17:907:9712:: with SMTP id jg18mr5265436ejc.328.1641932310998; 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: devicetree@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