Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp895775rwb; Tue, 29 Nov 2022 06:41:07 -0800 (PST) X-Google-Smtp-Source: AA0mqf6weXAL4GogHMZvXPB4KkWRAzwjS/afz1KM/3h7/0nrxiOwtGzOFrItcu3sLpECme4GWId0 X-Received: by 2002:a17:90b:1d45:b0:218:6db5:fd98 with SMTP id ok5-20020a17090b1d4500b002186db5fd98mr61567247pjb.164.1669732866766; Tue, 29 Nov 2022 06:41:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669732866; cv=none; d=google.com; s=arc-20160816; b=xrFQfhgBlC/JQ0KFm05abYs6U5xCF7vOvwOzidbuIVHRPck0Tv48r3IooEzmgjnq9u 5M2lOwKqkP/Sp1ORtvuhu/qExQhW75rwmk4jUZbd/vmb8nT1K4W0nBJlAi5LOLdNDEEF GULwurB48dFL8snXOKanLlZ/tiXv+oRPxgE9sBWsFRULTZgB+6FeR0WgbRfgCbKTS5Qd uRP9jgQHRrcLwS9bX3oSfbG84yjaC/2jCUD7/HMeiij2XFsjfoqVQ6sNzUTzr2y7zwsY gna3Ykmv9bAD6bSD2osZ2fchNc3ckZ5nVmeY1ezyNkEXwf6/PNYN3Vc4RrEfEEge9KBJ 10MQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=oBnRn3HsiMQKAOivFFQlQImQ7gVQuSe6GDXaOHch/qk=; b=K1+KhgYtauRChTjFkYod3Uwgs9Fhxj9uMCbgB00LsZ+TAQ0TGOs4/b8PljDZoFhLx0 oYfY1/aVVLbldKS/0dIoeJbYsm2kw1XJdCWkWKGQOfBkiXmtvlJ4tKsacD3W9nLgFs9G CvDYR7qUg8CnXnOwfZ9SiRsaA7YA2/wLLZeOvrhmPHfsZUF+xM1LRdVFYO+wJSqX0PkQ mEw7wWC3sSHnHqTOrFkc3Z512uKP/mPlTTMlIa86+fx+iZHIgbX8DcoCCArlWgWaLDuG rlgdP0EBjUCuA9cm5bPx5icRd/oIzYe8VSmcO3ZsRR0IqY9HLSE+vd9/rqQ9aVbkk2+V BWDw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ventanamicro.com header.s=google header.b="SdAecOq/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id f185-20020a636ac2000000b00477b463b042si13976235pgc.377.2022.11.29.06.40.54; Tue, 29 Nov 2022 06:41:06 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@ventanamicro.com header.s=google header.b="SdAecOq/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234792AbiK2ODw (ORCPT + 83 others); Tue, 29 Nov 2022 09:03:52 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38182 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234729AbiK2ODf (ORCPT ); Tue, 29 Nov 2022 09:03:35 -0500 Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BFB4524956 for ; Tue, 29 Nov 2022 06:03:33 -0800 (PST) Received: by mail-pl1-x62c.google.com with SMTP id d18so2689710pls.4 for ; Tue, 29 Nov 2022 06:03:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ventanamicro.com; s=google; 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=oBnRn3HsiMQKAOivFFQlQImQ7gVQuSe6GDXaOHch/qk=; b=SdAecOq/4TzlwSvwgp6xy/aimh7kAafCkzi9TimrB1Iua0Ohq4cGKMbU1/v6U3X/v3 gi1X+nkDc9XNapVheUoQ6MkkEu36/vjaGwpXr6EzpI3wg0R+v+5oDYK3OThVU1F+Gpmr 7NqAPqXCOvkar4MHdHWh4t8+hDlZHpMnzK1PEuNxAUq1FBAu2zUd1n2v3b0G9SPuJg1i x69dq/FDbXbogJnGr6Y63W1nSc49YdnlJqx7DAfespl/CW2c+Uter4eWV4oe2SrJrojb l4vrDcOF7w5BvnAz1CWbybwr90Wp4YiX19WR0RVj5tefk+TyX+mq7If5mSnxzx3x0wuL jQqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=oBnRn3HsiMQKAOivFFQlQImQ7gVQuSe6GDXaOHch/qk=; b=VmcWKY1MwkTprsJS89InkqAtoDETfxvWPe2IOuaJVFRhVZcGCoUa8FOG4WIfSrsO43 fmpEw5vXgIV2i7ZmSb6SQxayFtTUF4HgUONCKeNGXRyBapbaMawiJDS7jSIfqg1ghXuu zdWuE4sVsklgkmxitfTUI+6iB0hwowW0Zpu6trbXoI4YX3xWNemEheH/CMgbIvbtxfhJ PiQtSxmeWFBrjR8EIZ62+IXX9vbMym+WZM8jkOgXUMbpisWsXKI0OlKTsvzeF83Qq8GN k95+DZU6K0o6jbvp78QCfUSpuZJozpYSD6foyOPbhw8agQ2K+T6hXX9GrJElDzobA9Lf 290A== X-Gm-Message-State: ANoB5pkaIyRTbSISMhmC/kQ+I+oU5D1p6zXBNvz/fYvF3FNTr9tg8t1O CeCgem560B+IrUgk++3fPLsGoA== X-Received: by 2002:a17:90a:b703:b0:20d:7716:b05f with SMTP id l3-20020a17090ab70300b0020d7716b05fmr20514081pjr.104.1669730613158; Tue, 29 Nov 2022 06:03:33 -0800 (PST) Received: from anup-ubuntu-vm.localdomain ([171.76.84.98]) by smtp.gmail.com with ESMTPSA id k30-20020aa79d1e000000b00574f83c5d51sm6013747pfp.198.2022.11.29.06.03.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 29 Nov 2022 06:03:32 -0800 (PST) From: Anup Patel To: Rob Herring , Krzysztof Kozlowski , Palmer Dabbelt , Paul Walmsley , Daniel Lezcano , Thomas Gleixner Cc: Andrew Jones , Atish Patra , Samuel Holland , Conor Dooley , Anup Patel , devicetree@vger.kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, Anup Patel Subject: [PATCH v4 2/3] dt-bindings: timer: Add bindings for the RISC-V timer device Date: Tue, 29 Nov 2022 19:33:12 +0530 Message-Id: <20221129140313.886192-3-apatel@ventanamicro.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20221129140313.886192-1-apatel@ventanamicro.com> References: <20221129140313.886192-1-apatel@ventanamicro.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org We add DT bindings for a separate RISC-V timer DT node which can be used to describe implementation specific behaviour (such as timer interrupt not triggered during non-retentive suspend). Signed-off-by: Anup Patel Reviewed-by: Conor Dooley --- .../bindings/timer/riscv,timer.yaml | 52 +++++++++++++++++++ 1 file changed, 52 insertions(+) create mode 100644 Documentation/devicetree/bindings/timer/riscv,timer.yaml diff --git a/Documentation/devicetree/bindings/timer/riscv,timer.yaml b/Documentation/devicetree/bindings/timer/riscv,timer.yaml new file mode 100644 index 000000000000..cf53dfff90bc --- /dev/null +++ b/Documentation/devicetree/bindings/timer/riscv,timer.yaml @@ -0,0 +1,52 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/timer/riscv,timer.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: RISC-V timer + +maintainers: + - Anup Patel + +description: |+ + RISC-V platforms always have a RISC-V timer device for the supervisor-mode + based on the time CSR defined by the RISC-V privileged specification. The + timer interrupts of this device are configured using the RISC-V SBI Time + extension or the RISC-V Sstc extension. + + The clock frequency of RISC-V timer device is specified via the + "timebase-frequency" DT property of "/cpus" DT node which is described + in Documentation/devicetree/bindings/riscv/cpus.yaml + +properties: + compatible: + enum: + - riscv,timer + + interrupts-extended: + minItems: 1 + maxItems: 4096 # Should be enough? + + riscv,timer-cant-wake-cpu: + type: boolean + description: + If present, the timer interrupt can't wake up the CPU from + suspend/idle state. + +additionalProperties: false + +required: + - compatible + - interrupts-extended + +examples: + - | + timer { + compatible = "riscv,timer"; + interrupts-extended = <&cpu1intc 5>, + <&cpu2intc 5>, + <&cpu3intc 5>, + <&cpu4intc 5>; + }; +... -- 2.34.1