From: Ivan Bornyakov <i.bornyakov@metrotek.ru>
To: Xu Yilun <yilun.xu@intel.com>
Cc: mdf@kernel.org, hao.wu@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 v5 0/2] Lattice ECP5 FPGA manager
Date: Thu, 21 Jul 2022 11:54:11 +0300 [thread overview]
Message-ID: <20220721085411.ennvx74k45sxsimm@h-e2.ddg> (raw)
In-Reply-To: <20220721074431.GA1712998@yilunxu-OptiPlex-7050>
On Thu, Jul 21, 2022 at 03:44:31PM +0800, Xu Yilun wrote:
> On Tue, Jul 19, 2022 at 02:23:33PM +0300, Ivan Bornyakov wrote:
> > Add support to the FPGA manager for programming Lattice ECP5 FPGA over
> > slave SPI interface with .bit formatted uncompressed bitstream image.
>
> I didn't have time to looking into the patches yet, but I have some quick
> question.
>
> Where is the bitstream data writing to? To the FPGA active region or the
> backup nvmem like flash?
Bitstream is written to FPGA's volatile SRAM configuration memory.
>
> After reconfiguration, how to re-enumerate the hardware devices in the
> newly programmed FPGA region?
>
I personally describe FPGA-based devices statically in DT overlay within
fpga-region. Of course this approach is error prone to mismatch between
firmware and devices described in DT overlay...
> Thanks,
> Yilun
>
> >
> > ChangeLog:
> > v1 -> v2:
> > * remove "spi" from compatible string
> > * reword description in dt-bindings doc
> > * add reference to spi-peripheral-props.yaml in dt-binding doc
> > * fix DTS example in dt-bindings doc: 4-spaces indentations, no
> > undersores in node names.
> > v2 -> v3:
> > * fix typo "##size-cells" -> "#size-cells" in dt-bindings example
> > v3 -> v4:
> > * dt-bindings: reword description
> > * dt-bindings: revert props order
> > v4 -> v5:
> > * dt-bindings: remove trailing dot from title
> > * dt-bindings: reword description to avoid driver reference
> > * dt-bindings: add "Reviewed-by: Krzysztof Kozlowski" tag
> >
> > Ivan Bornyakov (2):
> > fpga: ecp5-spi: add Lattice ECP5 FPGA manager
> > dt-bindings: fpga: add binding doc for ecp5-spi fpga mgr
> >
> > .../bindings/fpga/lattice,ecp5-fpga-mgr.yaml | 74 +++++
> > drivers/fpga/Kconfig | 7 +
> > drivers/fpga/Makefile | 1 +
> > drivers/fpga/ecp5-spi.c | 275 ++++++++++++++++++
> > 4 files changed, 357 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/fpga/lattice,ecp5-fpga-mgr.yaml
> > create mode 100644 drivers/fpga/ecp5-spi.c
> >
> > --
> > 2.37.1
> >
next prev parent reply other threads:[~2022-07-21 8:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 11:23 Ivan Bornyakov
2022-07-19 11:23 ` [PATCH v5 1/2] fpga: ecp5-spi: add " Ivan Bornyakov
2022-07-29 12:41 ` Daniel Glöckner
2022-08-01 7:24 ` Daniel Glöckner
2022-08-09 6:54 ` Ivan Bornyakov
2022-07-19 11:23 ` [PATCH v5 2/2] dt-bindings: fpga: add binding doc for ecp5-spi fpga mgr Ivan Bornyakov
2022-07-29 9:01 ` Daniel Glöckner
2022-07-29 14:57 ` Xu Yilun
2022-07-29 16:33 ` Ivan Bornyakov
2022-07-29 17:49 ` Daniel Glöckner
2022-07-21 7:44 ` [PATCH v5 0/2] Lattice ECP5 FPGA manager Xu Yilun
2022-07-21 8:54 ` Ivan Bornyakov [this message]
2022-07-27 6:00 ` Ivan Bornyakov
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=20220721085411.ennvx74k45sxsimm@h-e2.ddg \
--to=i.bornyakov@metrotek.ru \
--cc=devicetree@vger.kernel.org \
--cc=hao.wu@intel.com \
--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
all inboxes | Powered by JetHome®