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 CA0A8C433EF for ; Fri, 14 Jan 2022 19:44:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229720AbiANToP (ORCPT ); Fri, 14 Jan 2022 14:44:15 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38380 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244108AbiANToO (ORCPT ); Fri, 14 Jan 2022 14:44:14 -0500 Received: from mail-ua1-x92a.google.com (mail-ua1-x92a.google.com [IPv6:2607:f8b0:4864:20::92a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5D087C06173F for ; Fri, 14 Jan 2022 11:44:14 -0800 (PST) Received: by mail-ua1-x92a.google.com with SMTP id p1so18738909uap.9 for ; Fri, 14 Jan 2022 11:44:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dJwo/s0+Rc0eQOHKUUuPigE1fDH9XGzotavYCOzNXD8=; b=VU4KUwt/Tr60y5OcD7lGeZ4iqhOuQpB0rJIp+JJDe9auj39wn0SNCqzCbSHPZZvZcm KzzpLJAUph0oIQtHvzda9jYDtk7yarbxgwScNzwthEuQSSAOs+8A1Tz7kOGBwqJeWBvS 8dxhsHVYZIUExjtrEz0jY2P6BRb9x6epZ/BCRM8RXUbuvqHOl4DRqEJAahzd12JhkbaM POQV/yAlb2eeZ8UrptPQRPyRCOj6D8O67lE5/jOhxOqZmjvOX4O311JM+518DkLY3VBX QgsGERpDbu3N1QZ6+XTgBVdbKmzbRlwAARQeqGVctyZxpPa2P3EX4Y6DgAxuye3QlCFS pdag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dJwo/s0+Rc0eQOHKUUuPigE1fDH9XGzotavYCOzNXD8=; b=roRswlPNn09e2FQj+emd611v3yr95RLAVvu70MPGesU4Rrsfes9sM5uvy/jqaZGyAR 9VKBt/htEEYIouCq1doJg140nC5Gt7Rx8xHhl++UQmVf88rm+6pM9VvFM6ouPn7zUw3B Fm7RuV5TzQLMIqxWWdoku+/hbDdyM1MuXAixlr3BEhGJeg047KKCV5KjnHaeYS/YFmTN xTW28pXyg+8gfgCltnlMIAxQuPqJC43rb3Al2iDMkyW32JCJXydEf40KkGEKH3C5FHlN y6AtcUP1IFxY1UYDaJFZbIepxWdyziT5x9CVpN8hu/TPbuY2Y9uj8piL3HCG3tzLbioI +byQ== X-Gm-Message-State: AOAM532zB5LlyJH5cxaJMl+OBiz7kRDyD62x4ylHC0ZitTpsK8OYPbSQ ZNiFRmpbkD0AQfrQA+CQIZUok+hS1f01VZl5H2qSTw== X-Google-Smtp-Source: ABdhPJzvX1gfxrvD0KqCKoIZ0gtEGerrArvAnqtuAR9K17w7Zmq/f6VA7N0SrwIXOGieZ8tG75VjrE+70/sbOWCKB84= X-Received: by 2002:ab0:13ee:: with SMTP id n43mr4749955uae.9.1642189453386; Fri, 14 Jan 2022 11:44:13 -0800 (PST) MIME-Version: 1.0 References: <20220111201426.326777-1-krzysztof.kozlowski@canonical.com> <20220111201722.327219-19-krzysztof.kozlowski@canonical.com> In-Reply-To: <20220111201722.327219-19-krzysztof.kozlowski@canonical.com> From: Sam Protsenko Date: Fri, 14 Jan 2022 21:44:00 +0200 Message-ID: Subject: Re: [PATCH v2 25/28] dt-bindings: pinctrl: samsung: describe Exynos850 and ExynosAutov9 wake-ups To: Krzysztof Kozlowski Cc: Tomasz Figa , 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, Marek Szyprowski , Chanho Park , Alim Akhtar Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Tue, 11 Jan 2022 at 22:18, Krzysztof Kozlowski wrote: > > 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 of their pin controller node capable of > external wake-up interrupts: > 1. No multiplexed external wake-up interrupt, only direct, > 2. More than one pin controller capable of external wake-up interrupts. > > Add dedicated Exynos850 and ExynosAutov9 compatibles. > > Signed-off-by: Krzysztof Kozlowski > --- Reviewed-by: Sam Protsenko > .../samsung,pinctrl-wakeup-interrupt.yaml | 27 ++++++++++++++++--- > 1 file changed, 24 insertions(+), 3 deletions(-) > > diff --git a/Documentation/devicetree/bindings/pinctrl/samsung,pinctrl-wakeup-interrupt.yaml b/Documentation/devicetree/bindings/pinctrl/samsung,pinctrl-wakeup-interrupt.yaml > index 6b684a53119b..a822f70f5702 100644 > --- a/Documentation/devicetree/bindings/pinctrl/samsung,pinctrl-wakeup-interrupt.yaml > +++ b/Documentation/devicetree/bindings/pinctrl/samsung,pinctrl-wakeup-interrupt.yaml > @@ -16,9 +16,12 @@ description: | > controller. > > External wake-up interrupts for Samsung S3C/S5P/Exynos SoC pin controller. > - Only one pin-controller device node can include external wake-up interrupts > - child node (in other words, only one External wake-up interrupts > + For S3C24xx, S3C64xx, S5PV210 and Exynos4210 compatible wake-up interrupt > + controllers, only one pin-controller device node can include external wake-up > + interrupts child node (in other words, only one External wake-up interrupts > pin-controller is supported). > + For newer controllers, multiple pin-controller device node can include > + external wake-up interrupts child node. > > See also Documentation/devicetree/bindings/pinctrl/samsung,pinctrl.yaml for > additional information and example. > @@ -32,6 +35,8 @@ properties: > - samsung,s5pv210-wakeup-eint > - samsung,exynos4210-wakeup-eint > - samsung,exynos7-wakeup-eint > + - samsung,exynos850-wakeup-eint > + - samsung,exynosautov9-wakeup-eint > > interrupts: > description: > @@ -41,7 +46,6 @@ properties: > > required: > - compatible > - - interrupts > > allOf: > - if: > @@ -56,6 +60,8 @@ allOf: > interrupts: > minItems: 6 > maxItems: 6 > + required: > + - interrupts > > - if: > properties: > @@ -67,6 +73,8 @@ allOf: > interrupts: > minItems: 4 > maxItems: 4 > + required: > + - interrupts > > - if: > properties: > @@ -81,5 +89,18 @@ allOf: > interrupts: > minItems: 1 > maxItems: 1 > + required: > + - interrupts > + > + - if: > + properties: > + compatible: > + contains: > + enum: > + - samsung,exynos850-wakeup-eint > + - samsung,exynosautov9-wakeup-eint > + then: > + properties: > + interrupts: false > > additionalProperties: false > -- > 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 6E4ABC433EF for ; Fri, 14 Jan 2022 19:45:29 +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:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=TeSduPeAxCtUSHorJZcbORTep3+KE0Ss3+Kq2ATm7Qk=; b=f6JlgUAkV1S7/T aN3XTE7nPZVk0SjvmAuNwDWNr5hXixPWqbncRVTpts0DFKitF49gHHpLVHTcZ8iDXptd1eyOLEEvE xcw5LSB0fBQNvux/oxZ3mlYHAOr3r1rk+tlTmnTdUVHPzy0YKVakL1rBwX5RqUv0En13nL58K2sCx JPTpXWfWZEF5wGAtRuhqDfMtaqZ8rqaLTJHp8u63ok+jZlLTwNSqu+rlwd5y/CEdCwwtQD//DQKkL 6hjWLv0Ej7qebOCj6CJ8+tedBk5baoIvnSo/XMrw52sgMUR+lYR/2JSw48ayc0AmQ/gxOfUsi6yXT JB6Wi+w5d8gwkExl+c2A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1n8SUk-00A6yg-90; Fri, 14 Jan 2022 19:44:18 +0000 Received: from mail-ua1-x930.google.com ([2607:f8b0:4864:20::930]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1n8SUg-00A6xi-4p for linux-arm-kernel@lists.infradead.org; Fri, 14 Jan 2022 19:44:15 +0000 Received: by mail-ua1-x930.google.com with SMTP id y4so18804117uad.1 for ; Fri, 14 Jan 2022 11:44:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dJwo/s0+Rc0eQOHKUUuPigE1fDH9XGzotavYCOzNXD8=; b=VU4KUwt/Tr60y5OcD7lGeZ4iqhOuQpB0rJIp+JJDe9auj39wn0SNCqzCbSHPZZvZcm KzzpLJAUph0oIQtHvzda9jYDtk7yarbxgwScNzwthEuQSSAOs+8A1Tz7kOGBwqJeWBvS 8dxhsHVYZIUExjtrEz0jY2P6BRb9x6epZ/BCRM8RXUbuvqHOl4DRqEJAahzd12JhkbaM POQV/yAlb2eeZ8UrptPQRPyRCOj6D8O67lE5/jOhxOqZmjvOX4O311JM+518DkLY3VBX QgsGERpDbu3N1QZ6+XTgBVdbKmzbRlwAARQeqGVctyZxpPa2P3EX4Y6DgAxuye3QlCFS pdag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dJwo/s0+Rc0eQOHKUUuPigE1fDH9XGzotavYCOzNXD8=; b=fjMurnPB4PbgJXqG7FWsHOpeVLRH2TyUoq436UiIZgT7KSKW/U+YvJwdzApfGOP9Xx dYEH9Rjx4IiZSyCeG3KBzO23vei12fuLWR0iWaB19UiHFkb2RCXDQmSFyG11wp4PXtou uxOJNaKuGNVXUmF7EHD8kqgCuHF6jifLDj5ikYc+4/XttCBFLPPrs1k56vMrni2QdKi1 GG1mV+5EPXrJJtrc8rT7l139D7D28hUCD95CJP9zQc0sXq7UUGfNnCdDaoe6zr6V5pIF J+nYkKy6VgAW4enKcjE9tv1khLx0oD8qois1jQPkcTu+vQHVBmGK80gIEjFxeeqn+y2P XVmw== X-Gm-Message-State: AOAM532BeZPO03KCmyU2quVp1CvRFjLfaOtBf+HwldcGzabythASSyf2 1jpDSxjmOglQ8jeWmGJ4p+duSCbR4RGc7ZOu9we4+g== X-Google-Smtp-Source: ABdhPJzvX1gfxrvD0KqCKoIZ0gtEGerrArvAnqtuAR9K17w7Zmq/f6VA7N0SrwIXOGieZ8tG75VjrE+70/sbOWCKB84= X-Received: by 2002:ab0:13ee:: with SMTP id n43mr4749955uae.9.1642189453386; Fri, 14 Jan 2022 11:44:13 -0800 (PST) MIME-Version: 1.0 References: <20220111201426.326777-1-krzysztof.kozlowski@canonical.com> <20220111201722.327219-19-krzysztof.kozlowski@canonical.com> In-Reply-To: <20220111201722.327219-19-krzysztof.kozlowski@canonical.com> From: Sam Protsenko Date: Fri, 14 Jan 2022 21:44:00 +0200 Message-ID: Subject: Re: [PATCH v2 25/28] dt-bindings: pinctrl: samsung: describe Exynos850 and ExynosAutov9 wake-ups To: Krzysztof Kozlowski Cc: Tomasz Figa , 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, Marek Szyprowski , Chanho Park , Alim Akhtar X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220114_114414_216593_9DBABE6E X-CRM114-Status: GOOD ( 18.52 ) 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 On Tue, 11 Jan 2022 at 22:18, Krzysztof Kozlowski wrote: > > 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 of their pin controller node capable of > external wake-up interrupts: > 1. No multiplexed external wake-up interrupt, only direct, > 2. More than one pin controller capable of external wake-up interrupts. > > Add dedicated Exynos850 and ExynosAutov9 compatibles. > > Signed-off-by: Krzysztof Kozlowski > --- Reviewed-by: Sam Protsenko > .../samsung,pinctrl-wakeup-interrupt.yaml | 27 ++++++++++++++++--- > 1 file changed, 24 insertions(+), 3 deletions(-) > > diff --git a/Documentation/devicetree/bindings/pinctrl/samsung,pinctrl-wakeup-interrupt.yaml b/Documentation/devicetree/bindings/pinctrl/samsung,pinctrl-wakeup-interrupt.yaml > index 6b684a53119b..a822f70f5702 100644 > --- a/Documentation/devicetree/bindings/pinctrl/samsung,pinctrl-wakeup-interrupt.yaml > +++ b/Documentation/devicetree/bindings/pinctrl/samsung,pinctrl-wakeup-interrupt.yaml > @@ -16,9 +16,12 @@ description: | > controller. > > External wake-up interrupts for Samsung S3C/S5P/Exynos SoC pin controller. > - Only one pin-controller device node can include external wake-up interrupts > - child node (in other words, only one External wake-up interrupts > + For S3C24xx, S3C64xx, S5PV210 and Exynos4210 compatible wake-up interrupt > + controllers, only one pin-controller device node can include external wake-up > + interrupts child node (in other words, only one External wake-up interrupts > pin-controller is supported). > + For newer controllers, multiple pin-controller device node can include > + external wake-up interrupts child node. > > See also Documentation/devicetree/bindings/pinctrl/samsung,pinctrl.yaml for > additional information and example. > @@ -32,6 +35,8 @@ properties: > - samsung,s5pv210-wakeup-eint > - samsung,exynos4210-wakeup-eint > - samsung,exynos7-wakeup-eint > + - samsung,exynos850-wakeup-eint > + - samsung,exynosautov9-wakeup-eint > > interrupts: > description: > @@ -41,7 +46,6 @@ properties: > > required: > - compatible > - - interrupts > > allOf: > - if: > @@ -56,6 +60,8 @@ allOf: > interrupts: > minItems: 6 > maxItems: 6 > + required: > + - interrupts > > - if: > properties: > @@ -67,6 +73,8 @@ allOf: > interrupts: > minItems: 4 > maxItems: 4 > + required: > + - interrupts > > - if: > properties: > @@ -81,5 +89,18 @@ allOf: > interrupts: > minItems: 1 > maxItems: 1 > + required: > + - interrupts > + > + - if: > + properties: > + compatible: > + contains: > + enum: > + - samsung,exynos850-wakeup-eint > + - samsung,exynosautov9-wakeup-eint > + then: > + properties: > + interrupts: false > > additionalProperties: false > -- > 2.32.0 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel