Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp2275976rwi; Fri, 21 Oct 2022 01:46:28 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7VstvnhsTUGc9QLBBfKZp6q/a07R3rRv1/1/QPqAuVKHnHDeMAJQQE2V4ASv4TeBZJlYeH X-Received: by 2002:a17:903:1110:b0:178:9f67:b524 with SMTP id n16-20020a170903111000b001789f67b524mr18493318plh.50.1666341988138; Fri, 21 Oct 2022 01:46:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666341988; cv=none; d=google.com; s=arc-20160816; b=glA9JZjD3bBXkoglAWQoJZUAu0TsA65MCmWRVwId+bp+BmLUE8pBzS2W68ftumkfox ft4qRwWaV38lyYW4tZsuFCuB45+hJGaz+ISbEUMgSQ9eJmh+N+kG6n1QyGtaKuVhU1+s mq48/hf30N6R1yFjlZ8fMee8LKWwf5miK70DD5qHo/+tNcT+E3GM+7XKngOdVs9bcl6+ FTffKcJLU2DYGo+HAiGLhgohyeLE/5xEQGLa6eFLYIocP+vtAuUr5CZRWAP57CDM4CBM xbwIOjXUeLqEgNrDfYTdiwmSFzwfoELIDhTsZ7lQKDZxugjSy3Hsm7u2m/2fGNZvCob9 SU4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:from:date:dkim-signature; bh=RKnwnZJ5hpitbXO/6ivBAV3jfi/Zk+UUEwGYstG9bts=; b=Qoy4odO+BVb1m8uHAwAPlc79cNX9z1ZJGLcCfe2f2XEvHtgdbCGDDrzcuWvE6WQcmV JVjmW1XATtrLBGggO20xZgMx71Bl13LheQKCjRO+eKPXMkbMBKbhx25AuzDHZSNDXsrJ BwPXDtyBi+MKsC8DGwmxkB4hzV8y+DupCPxfnsPrWpxCRuykFppRC9gA0+XD5ocpnqEN f3dx620OJzFkqrfkgRPQUnYwP1c/aeU8c6wlvy+j8hdFZS33P7lzf4vVoGvpj4c+upnu 1sWMxMJm81IlPlfsfdWipVdJWLFsUlN0jPocWsVnq0ecFOl0Cagba1PLELPatJp3gqeb HWVA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=hryA19he; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q36-20020a17090a752700b0020c2253cbc2si6372072pjk.54.2022.10.21.01.46.16; Fri, 21 Oct 2022 01:46:28 -0700 (PDT) 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=@intel.com header.s=Intel header.b=hryA19he; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230247AbiJUIg5 (ORCPT + 99 others); Fri, 21 Oct 2022 04:36:57 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46972 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230229AbiJUIgv (ORCPT ); Fri, 21 Oct 2022 04:36:51 -0400 Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 475BBC8202; Fri, 21 Oct 2022 01:36:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1666341389; x=1697877389; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=zahJ8vhDnJEtthrRXwrJff5QhUJx/GQgnc+lsUbnpJ8=; b=hryA19hedhEhB0L7q/ygyVp7E6/bwLMPoq61rKBucpm/r5/IlUVUH78A GZZyvKaTLD/zJezKiFFCyfbAcaQy4bzjjkEwL5her5OiIP84szXWFC9Nb SWKJBa50QQvblwd0VS13UrOqumrikh9YOrSMVG10ai7Vj3oJYvKZJbE8P Z7M+79M9JTQ8OtXV4WS1yrtxdUin954Qjte/7eGKfaV/6cJxtKEyM+uUP scVObgB7n17HCF8GhEG5mqZ01fsla5P4yc3Ef7a8Z287Ncm2AM5zzS8D8 aZaALKbXrATJd3WkDjTHZFC7OJEH4OnaIYW/Oo7pIAL4KpSewOLvBAnNB Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10506"; a="294347457" X-IronPort-AV: E=Sophos;i="5.95,200,1661842800"; d="scan'208";a="294347457" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Oct 2022 01:36:20 -0700 X-IronPort-AV: E=McAfee;i="6500,9779,10506"; a="735421533" X-IronPort-AV: E=Sophos;i="5.95,200,1661842800"; d="scan'208";a="735421533" Received: from lramir2-mobl1.ger.corp.intel.com ([10.252.44.179]) by fmsmga002-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Oct 2022 01:36:14 -0700 Date: Fri, 21 Oct 2022 11:36:10 +0300 (EEST) From: =?ISO-8859-15?Q?Ilpo_J=E4rvinen?= To: Matthew Gerlach cc: hao.wu@intel.com, yilun.xu@intel.com, russell.h.weight@intel.com, basheer.ahmed.muddebihal@intel.com, trix@redhat.com, mdf@kernel.org, linux-fpga@vger.kernel.org, linux-doc@vger.kernel.org, LKML , tianfei.zhang@intel.com, corbet@lwn.net, Greg Kroah-Hartman , linux-serial , Jiri Slaby , geert+renesas@glider.be, Andy Shevchenko , niklas.soderlund+renesas@ragnatech.se, macro@orcam.me.uk, johan@kernel.org, Lukas Wunner , marpagan@redhat.com Subject: Re: [PATCH v4 1/4] Documentation: fpga: dfl: Add documentation for DFHv1 In-Reply-To: Message-ID: <9511e1f-f927-7c45-1ab8-90587f9c91e4@linux.intel.com> References: <20221020212610.697729-1-matthew.gerlach@linux.intel.com> <20221020212610.697729-2-matthew.gerlach@linux.intel.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323329-1042773177-1666341379=:1761" X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE, URIBL_BLOCKED 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 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-1042773177-1666341379=:1761 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT On Fri, 21 Oct 2022, Ilpo J?rvinen wrote: > On Thu, 20 Oct 2022, matthew.gerlach@linux.intel.com wrote: > > > From: Matthew Gerlach > > > > Add documentation describing the extensions provided by Version > > 1 of the Device Feature Header (DFHv1). > > > > Signed-off-by: Matthew Gerlach > > --- > > v4: Remove marketing speak and separate v0 and v1 descriptions. > > Fix errors reported by "make htmldocs". > > > > v3: no change > > > > v2: s/GUILD/GUID/ > > add picture > > --- > > Documentation/fpga/dfl.rst | 96 ++++++++++++++++++++++++++++++++++++++ > > 1 file changed, 96 insertions(+) > > > > diff --git a/Documentation/fpga/dfl.rst b/Documentation/fpga/dfl.rst > > index 15b670926084..12365be435a8 100644 > > --- a/Documentation/fpga/dfl.rst > > +++ b/Documentation/fpga/dfl.rst > > @@ -561,6 +561,102 @@ new DFL feature via UIO direct access, its feature id should be added to the > > driver's id_table. > > > > > > +Device Feature Header - Version 0 > > +=========================================== > > +The format of Version 0 of a Device Feature Header (DFH) is shown below:: > > + > > + +-----------------------------------------------------------------------+ > > + |63 Type 60|59 DFH VER 52|51 Rsvd 41|40 EOL|39 Next 16|15 VER 12|11 ID 0| 0x00 > > + +-----------------------------------------------------------------------+ > > + |63 GUID_L 0| 0x08 > > + +-----------------------------------------------------------------------+ > > + |63 GUID_H 0| 0x10 > > + +-----------------------------------------------------------------------+ > > + > > +Offset 0x00 > > +Type - The type of DFH (e.g. FME, AFU, or private feature). > > +DFH VER - The version of the DFH. > > +Rsvd - Currently unused. > > +EOL - Set if this DFH is the end of the Device Feature List (DFL). > > +Next - The offset of the next DFH in the DFL from the start of the DFH. > > +If EOL is set, Next refers to size of mmio for last feature in the list. > > +ID - If Type field is 'private feature', then ID of the private feature. > > + > > +Offset 0x08 > > +GUID_L - Least significant 64 bits of a 128 bit Globally Unique Identifier > > +if Type is FME or AFU. > > + > > +Offset 0x10 > > +GUID_H - Most significant 64 bits of a 128 bit Globally Unique Identifier > > +if Type is FME or AFU. > > + > > + > > +Device Feature Header - Version 1 > > +=========================================== > > While this is structurally better than the previous one. I'd still include > at least one paragraph about the purpose. Something along these lines > (picked from v3 + edited the marketing speak/v0 compare away from it): > > Version 1 of the Device Feature Header (DFHv1) provides flexibility and > extensibility to hardware designs using Device Feature Lists. It is a > standardized mechanism for features to describe parameters/capabilities to > software. > > With DFHv1: > * GUID is mandatory for all types > * The register space of the feature is decoupled from the location of the DFH > * A list of parameter values associates to a particular feature. > > After that, the header itself makes much more sense already. > > > +The format of Version 1 of a Device Feature Header (DFH) is shown below:: > > + > > + +-----------------------------------------------------------------------+ > > + |63 Type 60|59 DFH VER 52|51 Rsvd 41|40 EOL|39 Next 16|15 VER 12|11 ID 0| 0x00 > > + +-----------------------------------------------------------------------+ > > + |63 GUID_L 0| 0x08 > > + +-----------------------------------------------------------------------+ > > + |63 GUID_H 0| 0x10 > > + +-----------------------------------------------------------------------+ > > + |63 Address/Offset 1| Rel 0| 0x18 > > Should this mention it's addr/offs of registers? As is it's bit hard to > figure out from the diagram w/o the extra description. I think you have > plenty of space for adding that extra bit of info. > > > + +-----------------------------------------------------------------------+ > > + |63 Reg Size 32|Params 31|30 Group 16|15 Instance 0| 0x20 > > + +-----------------------------------------------------------------------+ > > + |63 Next 34|RSV33|EOP32|31 Param Version 16|15 Param ID 0| 0x28 > > + +-----------------------------------------------------------------------+ > > + |63 Parameter Data 0| 0x30 > > + +-----------------------------------------------------------------------+ > > + > > + ... > > + > > + +-----------------------------------------------------------------------+ > > + |63 Next parameter offset 32|31 Param Version 16|15 Param ID 0| Copy-paste error on the next field. -- i. > > + +-----------------------------------------------------------------------+ > > + |63 Parameter Data 0| > > + +-----------------------------------------------------------------------+ > > + > > +Offset 0x00 > > +Type - The type of DFH (e.g. FME, AFU, or private feature). > > +DFH VER - The version of the DFH. > > +Rsvd - Currently unused. > > +EOL - Set if this DFH is the end of the Device Feature List (DFL). > > +Next - The offset of the next DFH in the DFL from the start of the DFH. > > +If EOL is set, Next refers to size of mmio for last feature in the list. > > +ID - If Type field is 'private feature', then ID of the private feature. > > + > > +Offset 0x08 > > +GUID_L - Least significant 64 bits of a 128 bit Globally Unique Identifier. > > + > > +Offset 0x10 > > +GUID_H - Most significant 64 bits of a 128 bit Globally Unique Identifier > > +if Type is FME or AFU. > > A copy-paste error? > > > + > > +Offset 0x18 > > +Address/Offset - If Rel bit is set, then high 63 bits of a 16 bit aligned > > +absolute address for the location of the feature's registers. > > +If Rel bit is clear, then the feature's registers start at the > > +offset from the start of the DFH. > > + > > +Offset 0x20 > > +Reg Size - Size of feature's register set. > > +Params - Set if DFH has one or more parameter blocks. > > +Group - Id of group if feature is part of a group. > > +Instance - Id of instance of feature within a group. > > + > > +Offset 0x28 if feature has parameters > > +Next - High 30 bits of a 32 bit aligned offset to the next parameter block. > > +If EOP set, size of last parameter. > > +Param Version - Version of Param ID. > > +Param ID - ID of parameter. > > + > > +Offset 0x30 > > +Parameter Data - Parameter data whose size and format is defined by version > > +and ID of the parameter. > > I'd reverse the order and say "ID and version" (kind of major thing > first). > > > + > > Open discussion > > =============== > > FME driver exports one ioctl (DFL_FPGA_FME_PORT_PR) for partial reconfiguration > > > > --8323329-1042773177-1666341379=:1761--