Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp317091ybh; Wed, 15 Jul 2020 02:46:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwbQ6RlKt5F7GOcFPUt9VbwodMxC4VXHWOsy2x9tRPZ6AaaBsxLVOSsACk6mloXZTc3aL0/ X-Received: by 2002:aa7:d4ca:: with SMTP id t10mr8728643edr.244.1594806411731; Wed, 15 Jul 2020 02:46:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594806411; cv=none; d=google.com; s=arc-20160816; b=g2Psu6FnNm+FDTTl+6Kbk4fss70EJ9kDWw79Y7mgzzBtBErOArcUdLpHZS9PnDISM5 Ig65V+uHfXb960aLc8eWACA0VWW9PkX9/uhSrOhz3Cd/vVSyIGJ0ODVlsXa/UgaFPIDD C9CErXOANkV/AgAoKn7YLMDKHmNmjP1/QbgEUy9QJJtTqLjqgXjnCe5zZ/WU2/YGbfu1 OgsN11AhY9K7pDMS2smiidVGmv+Xx8FNehwwbLy/RMe8Zc0Nry/ekEsI1qg109lmnWyH BohoX9haJBSpOh58WQWopdMPCDURUqjM2Y7UUCPZqbDJrSdn4dqBw/yiDf0i83B2mzs/ EowQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=dovjsIZCextFaV96o/guHAk9LrwZpGqEDI3F/jS8NlE=; b=VdBatiRkv5S+ttP4l9erMsl2NJJEsgribIzd977aKoBZ1lROlGSROQc20Dx2OvfS8H kqUbbpZvZ8aTjV+h7GymvyRlOzN4ZFbEoJGn3DBr/mhHCsJa3zaMdNR9n09hpCUzgf9B XIKcvPWqemzFLO6sADfeeg+1QfvrkmHJ4Cd5yg1+h4S9L88D+nDl1Tfu2dKpytz71JLp va29dWCC5jCW6Xn3cZ5JIOyUGutylG3Me08v3L/D3ilDmHHyD3Oc3vfQFkhXfQzaCUGu Y4qM4qzLaF239qKx8aOXhhNvCs8bLQKFgwDxWJAKOmlDQ1nXWcw8s0/LtTiqAxW96w5L v9Zw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=XyNfuSTQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m26si1245915ejn.625.2020.07.15.02.46.27; Wed, 15 Jul 2020 02:46:51 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=XyNfuSTQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730655AbgGOJkZ (ORCPT + 99 others); Wed, 15 Jul 2020 05:40:25 -0400 Received: from lelv0143.ext.ti.com ([198.47.23.248]:48968 "EHLO lelv0143.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728043AbgGOJkZ (ORCPT ); Wed, 15 Jul 2020 05:40:25 -0400 Received: from fllv0034.itg.ti.com ([10.64.40.246]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id 06F9eLJD024509; Wed, 15 Jul 2020 04:40:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1594806021; bh=dovjsIZCextFaV96o/guHAk9LrwZpGqEDI3F/jS8NlE=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=XyNfuSTQHWjGvwXYiSkgDbb5VFV39qeOBXzMkGJnUAJmMn968w95r9Wy/vAp2Xo6D ea7m0W/v2SsuQUY0AQ5afihcXZqOXDP9Qw+nygze9RSz/pPIROUP9G80sCbwiBWdCY AF90RroCythT/14EkAQ2Mns2f7C0mrFuYubsaAhE= Received: from DFLE104.ent.ti.com (dfle104.ent.ti.com [10.64.6.25]) by fllv0034.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 06F9eKc7109581 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 15 Jul 2020 04:40:20 -0500 Received: from DFLE113.ent.ti.com (10.64.6.34) by DFLE104.ent.ti.com (10.64.6.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1979.3; Wed, 15 Jul 2020 04:40:19 -0500 Received: from lelv0326.itg.ti.com (10.180.67.84) by DFLE113.ent.ti.com (10.64.6.34) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1979.3 via Frontend Transport; Wed, 15 Jul 2020 04:40:20 -0500 Received: from [10.250.100.73] (ileax41-snat.itg.ti.com [10.172.224.153]) by lelv0326.itg.ti.com (8.15.2/8.15.2) with ESMTP id 06F9eHtV026277; Wed, 15 Jul 2020 04:40:17 -0500 Subject: Re: [PATCH next 1/6] dt-bindings: soc: ti: k3-ringacc: convert bindings to json-schema To: Rob Herring , Santosh Shilimkar CC: Peter Ujfalusi , Vinod Koul , Sekhar Nori , , , Vignesh Raghavendra , References: <20200701103030.29684-1-grygorii.strashko@ti.com> <20200701103030.29684-2-grygorii.strashko@ti.com> From: Grygorii Strashko Message-ID: Date: Wed, 15 Jul 2020 12:40:11 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <20200701103030.29684-2-grygorii.strashko@ti.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Rob, On 01/07/2020 13:30, Grygorii Strashko wrote: > Convert the K3 NavigatorSS Ring Accelerator bindings documentation to > json-schema. > > Cc: Rob Herring > Signed-off-by: Grygorii Strashko > --- > .../devicetree/bindings/soc/ti/k3-ringacc.txt | 59 ---------- > .../bindings/soc/ti/k3-ringacc.yaml | 102 ++++++++++++++++++ > 2 files changed, 102 insertions(+), 59 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/soc/ti/k3-ringacc.txt > create mode 100644 Documentation/devicetree/bindings/soc/ti/k3-ringacc.yaml > > diff --git a/Documentation/devicetree/bindings/soc/ti/k3-ringacc.txt b/Documentation/devicetree/bindings/soc/ti/k3-ringacc.txt > deleted file mode 100644 > index 59758ccce809..000000000000 > --- a/Documentation/devicetree/bindings/soc/ti/k3-ringacc.txt > +++ /dev/null > @@ -1,59 +0,0 @@ > -* Texas Instruments K3 NavigatorSS Ring Accelerator > - > -The Ring Accelerator (RA) is a machine which converts read/write accesses > -from/to a constant address into corresponding read/write accesses from/to a > -circular data structure in memory. The RA eliminates the need for each DMA > -controller which needs to access ring elements from having to know the current > -state of the ring (base address, current offset). The DMA controller > -performs a read or write access to a specific address range (which maps to the > -source interface on the RA) and the RA replaces the address for the transaction > -with a new address which corresponds to the head or tail element of the ring > -(head for reads, tail for writes). > - > -The Ring Accelerator is a hardware module that is responsible for accelerating > -management of the packet queues. The K3 SoCs can have more than one RA instances > - > -Required properties: > -- compatible : Must be "ti,am654-navss-ringacc"; > -- reg : Should contain register location and length of the following > - named register regions. > -- reg-names : should be > - "rt" - The RA Ring Real-time Control/Status Registers > - "fifos" - The RA Queues Registers > - "proxy_gcfg" - The RA Proxy Global Config Registers > - "proxy_target" - The RA Proxy Datapath Registers > -- ti,num-rings : Number of rings supported by RA > -- ti,sci-rm-range-gp-rings : TI-SCI RM subtype for GP ring range > -- ti,sci : phandle on TI-SCI compatible System controller node > -- ti,sci-dev-id : TI-SCI device id of the ring accelerator > -- msi-parent : phandle for "ti,sci-inta" interrupt controller > - > -Optional properties: > - -- ti,dma-ring-reset-quirk : enable ringacc / udma ring state interoperability > - issue software w/a > - > -Example: > - > -ringacc: ringacc@3c000000 { > - compatible = "ti,am654-navss-ringacc"; > - reg = <0x0 0x3c000000 0x0 0x400000>, > - <0x0 0x38000000 0x0 0x400000>, > - <0x0 0x31120000 0x0 0x100>, > - <0x0 0x33000000 0x0 0x40000>; > - reg-names = "rt", "fifos", > - "proxy_gcfg", "proxy_target"; > - ti,num-rings = <818>; > - ti,sci-rm-range-gp-rings = <0x2>; /* GP ring range */ > - ti,dma-ring-reset-quirk; > - ti,sci = <&dmsc>; > - ti,sci-dev-id = <187>; > - msi-parent = <&inta_main_udmass>; > -}; > - > -client: > - > -dma_ipx: dma_ipx@ { > - ... > - ti,ringacc = <&ringacc>; > - ... > -} > diff --git a/Documentation/devicetree/bindings/soc/ti/k3-ringacc.yaml b/Documentation/devicetree/bindings/soc/ti/k3-ringacc.yaml > new file mode 100644 > index 000000000000..ae33fc957141 > --- /dev/null > +++ b/Documentation/devicetree/bindings/soc/ti/k3-ringacc.yaml > @@ -0,0 +1,102 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +# Copyright (C) 2020 Texas Instruments Incorporated - http://www.ti.com/ > +%YAML 1.2 > +--- > +$id: "http://devicetree.org/schemas/soc/ti/k3-ringacc.yaml#" > +$schema: "http://devicetree.org/meta-schemas/core.yaml#" > + > +title: Texas Instruments K3 NavigatorSS Ring Accelerator > + > +maintainers: > + - Santosh Shilimkar > + - Grygorii Strashko > + > +description: | > + The Ring Accelerator (RA) is a machine which converts read/write accesses > + from/to a constant address into corresponding read/write accesses from/to a > + circular data structure in memory. The RA eliminates the need for each DMA > + controller which needs to access ring elements from having to know the current > + state of the ring (base address, current offset). The DMA controller > + performs a read or write access to a specific address range (which maps to the > + source interface on the RA) and the RA replaces the address for the transaction > + with a new address which corresponds to the head or tail element of the ring > + (head for reads, tail for writes). > + > + The Ring Accelerator is a hardware module that is responsible for accelerating > + management of the packet queues. The K3 SoCs can have more than one RA instances > + > +properties: > + compatible: > + items: > + - const: ti,am654-navss-ringacc > + > + reg: > + items: > + - description: real time registers regions > + - description: fifos registers regions > + - description: proxy gcfg registers regions > + - description: proxy target registers regions > + > + reg-names: > + items: > + - const: rt > + - const: fifos > + - const: proxy_gcfg > + - const: proxy_target > + > + msi-parent: true > + > + ti,num-rings: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: Number of rings supported by RA > + > + ti,sci-rm-range-gp-rings: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: TI-SCI RM subtype for GP ring range > + > + ti,sci: > + $ref: /schemas/types.yaml#definitions/phandle-array > + description: phandle on TI-SCI compatible System controller node > + > + ti,sci-dev-id: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: TI-SCI device id of the ring accelerator > + > + ti,dma-ring-reset-quirk: > + $ref: /schemas/types.yaml#definitions/flag > + description: | > + enable ringacc/udma ring state interoperability issue software w/a > + > +required: > + - compatible > + - reg > + - reg-names > + - msi-parent > + - ti,num-rings > + - ti,sci-rm-range-gp-rings > + - ti,sci > + - ti,sci-dev-id > + > +additionalProperties: false > + > +examples: > + - | > + bus { > + #address-cells = <2>; > + #size-cells = <2>; > + > + ringacc: ringacc@3c000000 { > + compatible = "ti,am654-navss-ringacc"; > + reg = <0x0 0x3c000000 0x0 0x400000>, > + <0x0 0x38000000 0x0 0x400000>, > + <0x0 0x31120000 0x0 0x100>, > + <0x0 0x33000000 0x0 0x40000>; > + reg-names = "rt", "fifos", "proxy_gcfg", "proxy_target"; > + ti,num-rings = <818>; > + ti,sci-rm-range-gp-rings = <0x2>; /* GP ring range */ > + ti,dma-ring-reset-quirk; > + ti,sci = <&dmsc>; > + ti,sci-dev-id = <187>; > + msi-parent = <&inta_main_udmass>; > + }; > + }; > I'd be very appreciated if you can provide your feedback here. -- Best regards, grygorii