linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Ivan Bornyakov <i.bornyakov@metrotek.ru>
Cc: mdf@kernel.org, hao.wu@intel.com, yilun.xu@intel.com,
	trix@redhat.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, linux-fpga@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	system@metrotek.ru
Subject: Re: [PATCH 2/2] dt-bindings: fpga: add binding doc for ecp5-spi fpga mgr
Date: Mon, 18 Jul 2022 15:06:18 +0200	[thread overview]
Message-ID: <2a96f734-010d-b42d-8418-715d7c420272@linaro.org> (raw)
In-Reply-To: <20220715100356.fwjomifweifn6zsr@h-e2.ddg>

On 15/07/2022 12:03, Ivan Bornyakov wrote:
> On Fri, Jul 15, 2022 at 11:33:54AM +0200, Krzysztof Kozlowski wrote:
>> On 14/07/2022 14:26, Ivan Bornyakov wrote:
>>> Add Device Tree Binding doc for Lattice ECP5 FPGA manager using slave
>>> SPI to load .bit formatted uncompressed bitstream image.
>>>
>>> Signed-off-by: Ivan Bornyakov <i.bornyakov@metrotek.ru>
>>> ---
>>>  .../fpga/lattice,ecp5-spi-fpga-mgr.yaml       | 71 +++++++++++++++++++
>>>  1 file changed, 71 insertions(+)
>>>  create mode 100644 Documentation/devicetree/bindings/fpga/lattice,ecp5-spi-fpga-mgr.yaml
>>>
>>> diff --git a/Documentation/devicetree/bindings/fpga/lattice,ecp5-spi-fpga-mgr.yaml b/Documentation/devicetree/bindings/fpga/lattice,ecp5-spi-fpga-mgr.yaml
>>> new file mode 100644
>>> index 000000000000..79868f9c84e2
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/fpga/lattice,ecp5-spi-fpga-mgr.yaml
>>> @@ -0,0 +1,71 @@
>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>> +%YAML 1.2
>>> +---
>>> +$id: http://devicetree.org/schemas/fpga/lattice,ecp5-spi-fpga-mgr.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: Lattice ECP5 FPGA manager.
>>> +
>>> +maintainers:
>>> +  - Ivan Bornyakov <i.bornyakov@metrotek.ru>
>>> +
>>> +description:
>>> +  Device Tree Bindings for Lattice ECP5 FPGA Manager using slave SPI to
>>> +  load the uncompressed bitstream in .bit format.
>>
>> s/Device Tree Bindings for//
>>
>> Instead describe the hardware you are adding bindings for. What is a
>> "Manager"? It is so broad and unspecific... It is some dedicated
>> hardware to communicate with FPGA or you just called this regular FPGA
>> interface exposed to the CPU/SoC?
>>
> 
> "FPGA Manager" is a kernel subsystem that exports a set of functions for
> programming an FPGA with a bitstream image.
> See Documentation/driver-api/fpga/fpga-mgr.rst

This is what you want to include in the bindings document? How is it
related to bindings? We do not talk about driver API but we talk about
hardware. Bindings are for the hardware.

> 
>>> +
>>> +properties:
>>> +  compatible:
>>> +    enum:
>>> +      - lattice,ecp5-spi-fpga-mgr
>>
>> Do not encode interface name in compatible so no "spi".
>>
> 
> Recently when I submitted FPGA manager for Microchip PolarFire, I was
> asked the opposite, to add "spi" in compatible. The reason was that FPGA
> can be programmed through other interfaces as well.

I don't see such comment from Rob (DT maintainer):
https://lore.kernel.org/all/?q=%22dt-bindings%3A+fpga%3A+add+binding+doc+for+microchip-spi+fpga+mgr%22

Can you point me to it?

Best regards,
Krzysztof

  reply	other threads:[~2022-07-18 13:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14 12:26 [PATCH 0/2] Lattice ECP5 FPGA manager Ivan Bornyakov
2022-07-14 12:26 ` [PATCH 1/2] fpga: ecp5-spi: add " Ivan Bornyakov
2022-07-14 12:26 ` [PATCH 2/2] dt-bindings: fpga: add binding doc for ecp5-spi fpga mgr Ivan Bornyakov
2022-07-15  9:33   ` Krzysztof Kozlowski
2022-07-15 10:03     ` Ivan Bornyakov
2022-07-18 13:06       ` Krzysztof Kozlowski [this message]
2022-07-18 13:46         ` Ivan Bornyakov
2022-07-18 14:41           ` Krzysztof Kozlowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2a96f734-010d-b42d-8418-715d7c420272@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hao.wu@intel.com \
    --cc=i.bornyakov@metrotek.ru \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=system@metrotek.ru \
    --cc=trix@redhat.com \
    --cc=yilun.xu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).