[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170608170024.3d2b69b7@crub>
Date: Thu, 8 Jun 2017 17:00:24 +0200
From: Anatolij Gustschin <agust@...x.de>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: linux-fpga@...r.kernel.org, Alan Tull <atull@...nel.org>,
Moritz Fischer <moritz.fischer@...us.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
matthew.gerlach@...ux.intel.com, yi1.li@...ux.intel.com
Subject: Re: [PATCH v5] fpga manager: Add Altera CvP driver
On Thu, 8 Jun 2017 17:44:19 +0300
Andy Shevchenko andy.shevchenko@...il.com wrote:
>On Thu, Jun 8, 2017 at 5:15 PM, Anatolij Gustschin <agust@...x.de> wrote:
>> On Thu, 8 Jun 2017 02:38:55 +0300
>> Andy Shevchenko andy.shevchenko@...il.com wrote:
>>>On Thu, Jun 8, 2017 at 2:09 AM, Anatolij Gustschin <agust@...x.de> wrote:
>>>> On Fri, 2 Jun 2017 20:43:21 +0300
>>>> Andy Shevchenko andy.shevchenko@...il.com wrote:
>
>>>Besides below comments, please, do
>>>
>>>s/VSEC_/VSE_/g
>>>
>>>for entire file.
>>>
>>>We are following PCI and Thunderbolt pattern for use of Vendor
>>>Specific Extended Capability.
>>
>> I can do it, but I'm just not getting why. The registers are named as VSEC
>> registers in the documentation, why should the code name them differently?
>
>Does your documentation decode VSEC abbreviation?
>What C stands for? Capability?
the CvP user guide talks about Vendor Specific Extended Capability (VSEC).
--
Anatolij
Powered by blists - more mailing lists