Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp177124pxb; Fri, 15 Jan 2021 10:10:25 -0800 (PST) X-Google-Smtp-Source: ABdhPJzKh+PgjzcWEKJRctIW5BHxuQWnZ6luKKDjq7DV7vOmcuArjgZuXe/N5LRb8j298WrmnPuK X-Received: by 2002:a17:907:104c:: with SMTP id oy12mr9593923ejb.503.1610734225321; Fri, 15 Jan 2021 10:10:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610734225; cv=none; d=google.com; s=arc-20160816; b=a/Y6S5PRUef3SW6FJykbdYOT2MtYv/2t58TH6GJhR+in8tq5bF/cMJ0kZz0tMJxTkV KmVsY92y9s/DOKFf7+DtsUTZwOnKSuqPUBT1AJj0fc4vUt9J3iUkR6uqcJeGyCSqPBb8 aiFWMfte37Z44ZQMMbONL9DPQQ9xfSWgWkGZa7uE/H3WuptH2h/R1f25RIn21xgBGuTm o20nVfmhaPLLiz2x9PbdeIzFhCvWWGdd3BlIZ1HluM7n+wGYPGKysrSYE2orqHgzH7p/ B87FecAxFM5sY8BGGATNf9jWwHEbDx84HsWhB5/bOTq0pDn5xW4FsSSr2vDAZZwvVULr 1/Ag== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=3Md7vRoyiKJc0iq4tJJs8CQ7dxbz/DxlqmE3R+5lMtE=; b=OCVM7j69nlgn4WJQanbVr0xIJVyUmD+zKQYZzG/P3XoXIN7/tCp0mKbqoA5owJMi/o TnEYOA7hn0SNKSCvHhfXixLsV/EpThntkZBK7NWQTHgK4x8WRvwZrLhUWxNf6BP0EpCO rhrRExDWYc2CxK8P2IxTlmCYtEHThDHLK5jiIgNyf7JRkrfHhfo+/UWxyXDZEfa02l9L tMfh8tQHE3BxMIPW9pPlbWhOu4aoDzbslaP1dakC/hbYyIcAYvfyZXrY+ER5JP95jRyn 8t3VUPMgoON4z5rNppGKbyLgcusRps3eHVG0nXMJNzwt6t3EL8Z5+b3/Stv4Z5rOIh// Nc6A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=BYvs5MlM; 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=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l25si4644122edq.484.2021.01.15.10.09.57; Fri, 15 Jan 2021 10:10:25 -0800 (PST) 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=@redhat.com header.s=mimecast20190719 header.b=BYvs5MlM; 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=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727229AbhAOSJF (ORCPT + 99 others); Fri, 15 Jan 2021 13:09:05 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:50613 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725818AbhAOSJE (ORCPT ); Fri, 15 Jan 2021 13:09:04 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1610734057; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3Md7vRoyiKJc0iq4tJJs8CQ7dxbz/DxlqmE3R+5lMtE=; b=BYvs5MlMUkJdZYEkNaImTE86tFj2DB2P1kXePOh7zsgj9Vx/xjao6TSGOg711b1vZlcX0K ruWiwRYK82dQsZ8bm+5s7Y+9pNMp+QLvxdARjamFHxkmiFeuk5cl/W9dVkHxwWnz/Lqtef bf5BoZz6iXFyMatwbCsGvQPUteqSwdg= Received: from mail-qt1-f199.google.com (mail-qt1-f199.google.com [209.85.160.199]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-536-_9lyEfZOPQu7UuzpVBRlfA-1; Fri, 15 Jan 2021 13:07:28 -0500 X-MC-Unique: _9lyEfZOPQu7UuzpVBRlfA-1 Received: by mail-qt1-f199.google.com with SMTP id e14so8031577qtr.8 for ; Fri, 15 Jan 2021 10:07:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=3Md7vRoyiKJc0iq4tJJs8CQ7dxbz/DxlqmE3R+5lMtE=; b=EG11bjLdBCx3dLhpNGWlbj/X/6VxvTFMF7qq2hnDC9FLANuY51fOoGkxJVc5Smmz9W wCxcGH9JYoU/CpDMPI6v2wyXAZpB7VujZQpHs142hXD9RU9rCNe0NVska/CodI+2hm0n 15u3c1TcuWbcrtINPJr7jQ4ShLEyXZAB1R0S+aTx/Gm7E0Q4cWNzIgUxdsZLyhnaMcsm fXwgV5hBMmZAo5lidVVGsHEZwGOjsIvIArOKpRjXNpM7oYjG94FR7QVDtDWR2OnrpuxP oFr26upOZwP4mC7YGwSH2KVlqYp3qc0MtNQZYQbtkdPNNRzvnrBFB8TS6LwRRuYGmYJU c20g== X-Gm-Message-State: AOAM532lNvbsljjnfJg50aLuviBOdod6GAbHj06kmvyBz3uyBKK6OunS lHQWPBD+SMLeBbfKitzkwp4BmG4m0mY68GD8Ip4kK+ii5jyE5KFC0bCUlsTVDZzfdxG0gBgH+dL 2Ubh8MkLApqBpouEngdSCWCvp X-Received: by 2002:ae9:d847:: with SMTP id u68mr13552520qkf.409.1610734048020; Fri, 15 Jan 2021 10:07:28 -0800 (PST) X-Received: by 2002:ae9:d847:: with SMTP id u68mr13552493qkf.409.1610734047725; Fri, 15 Jan 2021 10:07:27 -0800 (PST) Received: from trix.remote.csb (075-142-250-213.res.spectrum.com. [75.142.250.213]) by smtp.gmail.com with ESMTPSA id a203sm5516833qkb.31.2021.01.15.10.07.25 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 15 Jan 2021 10:07:27 -0800 (PST) Subject: Re: [PATCH 1/2] dt-bindings: fpga: Add compatible value for Xilinx DFX AXI shutdown manger To: Nava kishore Manne , mdf@kernel.org, robh+dt@kernel.org, michal.simek@xilinx.com, linux-fpga@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Cc: git@xilinx.com, chinnikishore369@gmail.com References: <20210115013431.27667-1-nava.manne@xilinx.com> From: Tom Rix Message-ID: <2dd1a504-9bb7-3bdb-028e-7edd0ed99668@redhat.com> Date: Fri, 15 Jan 2021 10:07:25 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <20210115013431.27667-1-nava.manne@xilinx.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/14/21 5:34 PM, Nava kishore Manne wrote: > This patch Adds compatible value for Xilinx Dynamic Function eXchnage(DFX) > AXI Shutdown manager IP. A multi patch set should have a cover letter. Use git format-patch --cover-letter > Signed-off-by: Nava kishore Manne > --- > .../bindings/fpga/xilinx-pr-decoupler.txt | 19 ++++++++++++++++--- > 1 file changed, 16 insertions(+), 3 deletions(-) > > diff --git a/Documentation/devicetree/bindings/fpga/xilinx-pr-decoupler.txt b/Documentation/devicetree/bindings/fpga/xilinx-pr-decoupler.txt > index 4284d293fa61..42fca058a5f4 100644 > --- a/Documentation/devicetree/bindings/fpga/xilinx-pr-decoupler.txt > +++ b/Documentation/devicetree/bindings/fpga/xilinx-pr-decoupler.txt > @@ -7,13 +7,26 @@ changes from passing through the bridge. The controller can also > couple / enable the bridges which allows traffic to pass through the > bridge normally. Below is some wordsmithing to make the compatibility explicit and remove unneeded words > > +Xilinx LogiCORE Dynamic Function eXchange(DFX) AXI shutdown manager > +Softcore is compatible with the Xilinx LogiCORE pr-decoupler. > + > +The Xilinx LogiCORE Dynamic Function eXchange(DFX) AXI shutdown manager > +manages one or more shutdown managers / fpga bridges. > +The controller can shutdown/passthrough the bridges which prevents Delete 4 lines above. The DFX AXI shutdown manager prevents > +AXI traffic from passing through the bridge. The controller safely > +handles AXI4MM and AXI4-Lite interfaces on a Reconfigurable Partition > +when it is undergoing dynamic reconfiguration (DFX), preventing system I don't know about the use of '(DFX)' here, above it is Dynamic Function eXchange' Here it is dynamic reconfiguration, maybe just delete the '(DFX)' > +deadlock that can occur if AXI transactions are interrupted by DFX > + > The Driver supports only MMIO handling. A PR region can have multiple > -PR Decouplers which can be handled independently or chained via decouple/ > -decouple_status signals. > +PR Decouplers/AXI shutdown manager which can be handled independently > +or chained via decouple/ decouple_status signals. Being compatible, i don't think it is necessary to add to / change this section. > > Required properties: > - compatible : Should contain "xlnx,pr-decoupler-1.00" followed by > - "xlnx,pr-decoupler" > + "xlnx,pr-decoupler" or > + "xlnx,dfx-axi-shutdown-manager-1.00" followed by > + "xlnx,dfx-axi-shutdown-manager" > - regs : base address and size for decoupler module > - clocks : input clock to IP > - clock-names : should contain "aclk" Adding an example similar to the existing would be helpful. Tom