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 6C904C433EF for ; Tue, 11 Jan 2022 20:19:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1350817AbiAKUTR (ORCPT ); Tue, 11 Jan 2022 15:19:17 -0500 Received: from smtp-relay-internal-1.canonical.com ([185.125.188.123]:38576 "EHLO smtp-relay-internal-1.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1346609AbiAKUSf (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 ACBBE4005A 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=kQHLxaxxJLFmOGqzWUxDRLkwO6oKafieScmNTdNr7i4=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=BU1KhsIk5nEo9RDu85jhtRKVIOUZcVwAfYcZikRHouzX3zNAI/mePRVn4N37jbOm2 rXdlhwhgMkKTTErl6AC136I5l0xWwXmCfRlnFqYlGfKfYinxzNouh1koeseUWLk9Wn 0oIZd1rn0JCMutTg6ooQ0ElauVZg11pvDWynvoc9oCVADU1fqeodJAPYeEIOKXUiik P7OlHR04IpiTAkuvpscpqT8ov2xNhOIj1hSBFbx7rCTRaobmu+7Py/cGNWA6m5PLKO fp7ejRioH7Pkl6d+hxKGmzg1cGWxxmHD1DO5J3v+YOMtYjyL7zfhCcO38ZvaATeMnl VW11YM+ja5W9Q== Received: by mail-ed1-f69.google.com with SMTP id l14-20020aa7cace000000b003f7f8e1cbbdso156073edt.20 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=kQHLxaxxJLFmOGqzWUxDRLkwO6oKafieScmNTdNr7i4=; b=gCoewRt2UehCblSX3/9fFEjN/V5vvTHZjwwxGVrs3WTZbFTyemFY/uQ8k9IJQSC43+ uWqkAVucnY/3JNo6hAp0pDyOllXWZkHZx3F01jveru/f9OcwisUp5QYwZHH/VU08tBkR Mb7sUmKYHXY+86ntLzbu2XcsJ+9cASXoTCZlxRfHx+Ft//vZueTjdaq2FMHRXpVdP24f YraJa3dfTpsBRJi6MfEBn52lnk/qM3rWRun0QzvnKkcENl4mDhruTjReAhPBT8rVld2X u1euP+dReK1yAAcbIsUVd9itw+seodMUlGUns4cfklr+nvcOWiHQBuohFxcrjXy9VopI DNsg== X-Gm-Message-State: AOAM5339kF97yHMNPxiwcswIU4Y/Xe84RCn2kSVqVyn6EQZczrsOujWM QPeKEQ0A9n/vYb+1iNjuug6jO26Rt7LkB0kRQlTZqEJRsV5v59WRLBA/dYxMYO9NSBf64OqdsTC AXK0cBF1aNfVt2yXTk/aWvTCIHD0wh8zwjVcHj30= X-Received: by 2002:a50:f086:: with SMTP id v6mr737738edl.94.1641932312220; Tue, 11 Jan 2022 12:18:32 -0800 (PST) X-Google-Smtp-Source: ABdhPJxJA2UIH8S5lzI4JycUQ9WDc6T41H+sPiiwxmzpWvqHdoH7V+UxlOdlH0f0srHDP5vkj+BfXg== X-Received: by 2002:a50:f086:: with SMTP id v6mr737711edl.94.1641932312024; Tue, 11 Jan 2022 12:18:32 -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.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Jan 2022 12:18:31 -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 28/28] arm64: dts: exynos: use dedicated wake-up pinctrl compatible in ExynosAutov9 Date: Tue, 11 Jan 2022 21:17:22 +0100 Message-Id: <20220111201722.327219-22-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-gpio@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 ExynosAutov9 compatible for its external wake-up interrupts controller to indicate the differences. Signed-off-by: Krzysztof Kozlowski --- arch/arm64/boot/dts/exynos/exynosautov9.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/exynos/exynosautov9.dtsi b/arch/arm64/boot/dts/exynos/exynosautov9.dtsi index de8fcb82eaec..807d500d6022 100644 --- a/arch/arm64/boot/dts/exynos/exynosautov9.dtsi +++ b/arch/arm64/boot/dts/exynos/exynosautov9.dtsi @@ -208,7 +208,7 @@ pinctrl_alive: pinctrl@10450000 { reg = <0x10450000 0x1000>; wakeup-interrupt-controller { - compatible = "samsung,exynos7-wakeup-eint"; + compatible = "samsung,exynosautov9-wakeup-eint"; }; }; -- 2.32.0 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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 03F7AC433F5 for ; Tue, 11 Jan 2022 20:39:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-Id:Date:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=1z1uQc0yWJGk5gkGNZ9h9iWPeluFt+ZEQ766/nKNVsM=; b=MUaamy5JXRdWIT 5ljRU2Tns+NB1eMR5YILKWH6t4a7s9AlfKRlhd0ZbemSsA6l9crVQpLB/xLLZZ5/PzQ+sgsxX1eB4 ZhMfWHzdFk9sjAhyIn8fmryyJ/SSUFi5bXHR/yuWH3MbVWgb6Iuab09kIUgzerHgGCXEJ2pxRoJcJ e8M09FMIkMQgQBKVZMrLDSY7T9eLFcUU86JNFCfckw1lRkBf/4+NczuEtqrph39ZU1NR1LVnl9tKa i8KcDucnzLr9UCbdly0Pt9RN6GGTlXIMstXVBLYlZje2Vfn/cnffRWBSRAgzTvwbv45Lm0O0hH5EM Gmg/+rU3Eln1AqZwdJWA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1n7Ntz-0003Vw-2Q; Tue, 11 Jan 2022 20:37:57 +0000 Received: from smtp-relay-internal-0.canonical.com ([185.125.188.122]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1n7NbG-00HXUO-Go for linux-arm-kernel@lists.infradead.org; Tue, 11 Jan 2022 20:18:37 +0000 Received: from mail-ed1-f72.google.com (mail-ed1-f72.google.com [209.85.208.72]) (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 B649B40AD9 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=kQHLxaxxJLFmOGqzWUxDRLkwO6oKafieScmNTdNr7i4=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=VeAGBk987DL99eyMA326D2qBmIp6pbLOyKqIahGvEtrCQcWtGZGsR7wfHQA2OvL+h IyLIoRdozt4bnkBE0/V25LMMX3rmcF1bd4Y+c3e5jFQLUWMUHjM7YuF4s+b33WrDSW QVKClLFciVl1JnMLAqk42iYL51KqHLSTJN/BVO9DnKat3Tse2NOEqNl9eFgYqRzfBU B7yJAkRSmlz5EMzjS8oG2y8rOzpHfOWbcPv/FnpSdYNZrIKVMqyHumRXrpkQeYWqHt fEfX+p6nu3eKdPAXlxF1LAgG6wUbbbS/j9yx9zjN82EwLFTplGw22Xrf6hq8fypzWy GWrK9L18+3NpA== Received: by mail-ed1-f72.google.com with SMTP id p8-20020aa7d308000000b003fe9b0c4760so166976edq.17 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=kQHLxaxxJLFmOGqzWUxDRLkwO6oKafieScmNTdNr7i4=; b=l3W3V2x+2T0nzYdA9unwe0CPw30lMiH3z5qVL5iFLs2GP2Iyx6ZdWQuTEZnNcrNd10 8vqToCvvMRP5Gm+u+q9Yu7zAe2TmhaZnM8og8RJ9f+orBb/4J4eYfb0OBnfdpI66Ol/7 1IEwm+PqNaczPIP5uufTweN660baXWorT/wSLo2HfWCv9xt3gWufL9wRZwz7v/zIs2Gp frcjU4zVEGEYvpEX1zvlguX9W0cM6+GZI/nhxHRSqjBoFauLrJ9ULAo5+JkS7VPLX9bZ gDFDdlrTBwrO93516oFICj4TvimIE01zvJBJUlb7cztyLEptNQjDfA10MMePneGV/GcS Lbsg== X-Gm-Message-State: AOAM533J1v0C7Ka55BpIvf1bpH0Ud9QFDVRPldlDVYXmygp09pbGJlks RNZBPzdHEwUW+EA27IAGAjRT87YdsbOkRHR4UhQ+rA9R67qNStDaFkO0lbgqCOg7mD4XeUVB8HF 65VrwsRphZqUO/ryi1TLIzeTR5wKMJMX7xezMs98K3W+vK/9wByD+ X-Received: by 2002:a50:f086:: with SMTP id v6mr737740edl.94.1641932312220; Tue, 11 Jan 2022 12:18:32 -0800 (PST) X-Google-Smtp-Source: ABdhPJxJA2UIH8S5lzI4JycUQ9WDc6T41H+sPiiwxmzpWvqHdoH7V+UxlOdlH0f0srHDP5vkj+BfXg== X-Received: by 2002:a50:f086:: with SMTP id v6mr737711edl.94.1641932312024; Tue, 11 Jan 2022 12:18:32 -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.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Jan 2022 12:18:31 -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 28/28] arm64: dts: exynos: use dedicated wake-up pinctrl compatible in ExynosAutov9 Date: Tue, 11 Jan 2022 21:17:22 +0100 Message-Id: <20220111201722.327219-22-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 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220111_121834_772264_484977ED X-CRM114-Status: GOOD ( 15.08 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.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 ExynosAutov9 compatible for its external wake-up interrupts controller to indicate the differences. Signed-off-by: Krzysztof Kozlowski --- arch/arm64/boot/dts/exynos/exynosautov9.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/exynos/exynosautov9.dtsi b/arch/arm64/boot/dts/exynos/exynosautov9.dtsi index de8fcb82eaec..807d500d6022 100644 --- a/arch/arm64/boot/dts/exynos/exynosautov9.dtsi +++ b/arch/arm64/boot/dts/exynos/exynosautov9.dtsi @@ -208,7 +208,7 @@ pinctrl_alive: pinctrl@10450000 { reg = <0x10450000 0x1000>; wakeup-interrupt-controller { - compatible = "samsung,exynos7-wakeup-eint"; + compatible = "samsung,exynosautov9-wakeup-eint"; }; }; -- 2.32.0 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel