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, dg@emlix.com,
j.zink@pengutronix.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-fpga@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de, system@metrotek.ru
Subject: Re: [PATCH v20 1/2] fpga: lattice-sysconfig-spi: add Lattice sysCONFIG FPGA manager
Date: Tue, 25 Oct 2022 14:11:54 +0300 [thread overview]
Message-ID: <20221025111154.d4o6hvya2fb6hmev@h-e2.ddg> (raw)
In-Reply-To: <Y1eILk6ArO5OVzwW@yilunxu-OptiPlex-7050>
On Tue, Oct 25, 2022 at 02:54:38PM +0800, Xu Yilun wrote:
> On 2022-10-25 at 08:39:46 +0300, Ivan Bornyakov wrote:
> > Add support to the FPGA manager for programming Lattice ECP5 FPGA over
> > slave SPI sysCONFIG interface.
> >
> > sysCONFIG interface core functionality is separate from both ECP5 and
> > SPI specifics, so support for other FPGAs with different port types can
> > be added in the future.
> >
> > Signed-off-by: Ivan Bornyakov <i.bornyakov@metrotek.ru>
>
> [...]
>
> > +static int sysconfig_spi_bitstream_burst_init(struct sysconfig_priv *priv)
> > +{
> > + const u8 lsc_bitstream_burst[] = SYSCONFIG_LSC_BITSTREAM_BURST;
> > + struct spi_device *spi = to_spi_device(priv->dev);
> > + struct spi_transfer xfer = {};
> > + struct spi_message msg;
> > + size_t buf_len;
> > + void *buf;
> > + int ret;
> > +
> > + buf_len = sizeof(lsc_bitstream_burst);
> > +
> > + buf = kmemdup(lsc_bitstream_burst, buf_len, GFP_KERNEL);
> > + if (!buf)
> > + return -ENOMEM;
> > +
> > +
>
> I removed the second blank line and applied this series to for-next.
>
Sorry for this negligence. Thanks.
next prev parent reply other threads:[~2022-10-25 11:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 5:39 [PATCH v20 0/2] Lattice sysCONFIG SPI FPGA manager Ivan Bornyakov
2022-10-25 5:39 ` [PATCH v20 1/2] fpga: lattice-sysconfig-spi: add Lattice sysCONFIG " Ivan Bornyakov
2022-10-25 6:54 ` Xu Yilun
2022-10-25 11:11 ` Ivan Bornyakov [this message]
2022-10-25 5:39 ` [PATCH v20 2/2] dt-bindings: fpga: document " 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=20221025111154.d4o6hvya2fb6hmev@h-e2.ddg \
--to=i.bornyakov@metrotek.ru \
--cc=devicetree@vger.kernel.org \
--cc=dg@emlix.com \
--cc=hao.wu@intel.com \
--cc=j.zink@pengutronix.de \
--cc=kernel@pengutronix.de \
--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