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 ACA8DC433EF for ; Wed, 29 Jun 2022 10:07:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231194AbiF2KHU (ORCPT ); Wed, 29 Jun 2022 06:07:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51184 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229861AbiF2KHU (ORCPT ); Wed, 29 Jun 2022 06:07:20 -0400 Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 46C1D3DA6A for ; Wed, 29 Jun 2022 03:07:19 -0700 (PDT) Received: by mail-ej1-x629.google.com with SMTP id pk21so31582956ejb.2 for ; Wed, 29 Jun 2022 03:07:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=UI9cYbOS287xUrQaY8UIv5U4S9Lu0ZwNP7V9PXH0PV4=; b=NCZHWN/cJfm3yny65P8YlLhwiDOO26ZGNIOI86H8qkah4/8sC2HH4UF0vcAQBvnhR/ JuzFrPrnGn7/VJSNEfJGL45unlg7C7ye2LcicTxY0l/+dyalv/069wFcagPKFYOMcQeK V4zFV6PwhuwiL7Ra/0J9qJQ9BW26dVMAgqP8dqpYZgVm4srrH/kUApqswi6gyA64RmDs MSGD66lRTRCTNHu0f2FfNzS7Acg9ZA1hk568F7ku7Jt1AkKOYJTLkXLYKx1qqKfx/hov HPA146AMhxsHv1o9tnYM3yyQiPcUSYNYlvNaUjBw6ZkDxFMyQ4ktdIoL/Q+HXWFZg9XQ lTDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=UI9cYbOS287xUrQaY8UIv5U4S9Lu0ZwNP7V9PXH0PV4=; b=MNHc0QkH+k2YzXll1lCJayDBUgf/EDOPNPisYcyzgG1lZQV+WnJw6cA0YZLPiNw8RG njqkVyvKnvRRy6z7hGmRXd1TW1npmyFAh7PPWhyhT2MfgxhOztmkLj8rfYHmj2WPbl4H zbN4+kC+i8JdUYNxkBeSGvCdPfWO/8rCXitH++eR2Hx5wsSj/PZrtAqdhSQlVKOBEpEA SSFCkYIwAJKLjEq/dS61WAowujmHvmVyZH9NmSAw5GAhXrAK1wjL0wGji93QvqjbaeCC 0E19cnatnULZelzAUeHKwz9r1wK97aAzGt5GNzdm+FrE+Ec2zGqhCXWyCLrDwuS15YT4 CLWg== X-Gm-Message-State: AJIora+N8AWz6zjTRa0wLkb7H9/i551m5sKY0eRXCv8xCQzR+Y07n8/h Mvl0H2g3JAhtn9PBGOjol79bQQ== X-Google-Smtp-Source: AGRyM1t88ZULBHs8ccIHaDmNBddyVX1Qha12QXv8ndf/tZldlCtfEPBLrfk8gfi9BQDElKx1RSrzJw== X-Received: by 2002:a17:907:c1d:b0:726:3239:fe83 with SMTP id ga29-20020a1709070c1d00b007263239fe83mr2513343ejc.51.1656497237837; Wed, 29 Jun 2022 03:07:17 -0700 (PDT) Received: from [192.168.0.183] (xdsl-188-155-176-92.adslplus.ch. [188.155.176.92]) by smtp.gmail.com with ESMTPSA id k25-20020a170906971900b00724e6a55d1asm7469511ejx.197.2022.06.29.03.07.16 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 29 Jun 2022 03:07:17 -0700 (PDT) Message-ID: Date: Wed, 29 Jun 2022 12:07:16 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: [PATCH 1/4] dt-bindings: misc: tmr-manager: Add device-tree binding for TMR Manager Content-Language: en-US To: Appana Durga Kedareswara rao , robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, michal.simek@xilinx.com, derek.kiernan@xilinx.com, dragan.cvetic@xilinx.com, arnd@arndb.de, gregkh@linuxfoundation.org, linux-arm-kernel@lists.infradead.org Cc: git@amd.com, git@xilinx.com References: <20220628054338.1631516-1-appana.durga.rao@xilinx.com> <20220628054338.1631516-2-appana.durga.rao@xilinx.com> From: Krzysztof Kozlowski In-Reply-To: <20220628054338.1631516-2-appana.durga.rao@xilinx.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 28/06/2022 07:43, Appana Durga Kedareswara rao wrote: > This commit adds documentation for Triple Modular Redundancy(TMR) Manager > IP. The Triple Modular Redundancy(TMR) Manager is responsible for handling > the TMR subsystem state, including fault detection and error recovery > provides soft error detection, correction and recovery features. > > Signed-off-by: Appana Durga Kedareswara rao > --- > .../bindings/misc/xlnx,tmr-manager.yaml | 48 +++++++++++++++++++ This is not a misc device. Find appropriate subsystem for it. It's not EDAC, right? > 1 file changed, 48 insertions(+) > create mode 100644 Documentation/devicetree/bindings/misc/xlnx,tmr-manager.yaml > > diff --git a/Documentation/devicetree/bindings/misc/xlnx,tmr-manager.yaml b/Documentation/devicetree/bindings/misc/xlnx,tmr-manager.yaml > new file mode 100644 > index 000000000000..f6cb4d235981 > --- /dev/null > +++ b/Documentation/devicetree/bindings/misc/xlnx,tmr-manager.yaml > @@ -0,0 +1,48 @@ > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/misc/xlnx,tmr-manager.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Xilinx TMR Microblaze Device Tree Bindings s/Device Tree Bindings// > + > +maintainers: > + - Appana Durga Kedareswara rao > + > +description: | > + The Triple Modular Redundancy(TMR) Manager is responsible for handling the > + TMR subsystem state, including fault detection and error recovery. The core > + is triplicated in each of the sub-blocks in the TMR subsystem, and provides > + majority voting of its internal state. > + > +properties: > + compatible: > + enum: > + - xlnx,tmr-manager-1.0 > + > + reg: > + maxItems: 1 > + > + xlnx,magic1: > + minimum: 0 > + maximum: 255 > + description: > + Magic number 1, When writing to the control register the first write data > + byte (bits 7:0) must match this value in order to have any effect on the > + nominal recovery function. Register values are usually not in the scope of bindings. We describe here hardware, not programming model, although in case of soft cores maybe it's a bit different. Anyway you need to describe the actual feature, not OS behavior. > + $ref: /schemas/types.yaml#/definitions/uint32 > + > +required: > + - compatible > + - reg > + - xlnx,magic1 > + > +additionalProperties: false > + > +examples: > + - | > + tmr-manager@44a10000 { Depending on what is this, you should use appropriate generic node name. > + compatible = "xlnx,tmr-manager-1.0"; > + reg = <0x44a10000 0x10000>; > + xlnx,magic1 = <0x46>; > + }; Best regards, Krzysztof