From: "Daniel Glöckner" <dg@emlix.com>
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 v5 1/2] fpga: ecp5-spi: add Lattice ECP5 FPGA manager
Date: Fri, 29 Jul 2022 14:41:44 +0200 [thread overview]
Message-ID: <20220729124143.GA31715@homes.emlix.com> (raw)
In-Reply-To: <20220719112335.9528-2-i.bornyakov@metrotek.ru>
Hi,
On Tue, Jul 19, 2022 at 02:23:34PM +0300, Ivan Bornyakov wrote:
> + struct spi_transfer lsc_xfers[] = {
> + {
> + .tx_buf = lsc_init_addr,
> + .len = sizeof(lsc_init_addr),
> + .cs_change = 1,
> + }, {
> + .tx_buf = lsc_bitstream_burst,
> + .len = sizeof(lsc_bitstream_burst),
> + .cs_change = 1,
> + },
> + };
cs_change in the last transfer of a message will not prevent transfers
with other spi devices on the bus from taking place. You want to use
spi_bus_lock and friends in addition.
Best regards,
Daniel
next prev parent reply other threads:[~2022-07-29 12:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 11:23 [PATCH v5 0/2] " 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 [this message]
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
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=20220729124143.GA31715@homes.emlix.com \
--to=dg@emlix.com \
--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
all inboxes | Powered by JetHome®