From: Xu Yilun <yilun.xu@intel.com>
To: Johannes Zink <j.zink@pengutronix.de>
Cc: linux-fpga@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>, Moritz Fischer <mdf@kernel.org>,
Wu Hao <hao.wu@intel.com>,
kernel@pengutronix.de
Subject: Re: [PATCH 15/16] fpga: machxo2: extend erase timeout for machxo2 FPGA
Date: Mon, 29 Aug 2022 17:26:48 +0800 [thread overview]
Message-ID: <YwyGWELZ7WfCE3FS@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <20220825141343.1375690-16-j.zink@pengutronix.de>
On 2022-08-25 at 16:13:42 +0200, Johannes Zink wrote:
> Measurements showed that some FPGAs take significantly longer than the
> default wait function supplied. The datasheet inidicates up to 30
> seconds erase times for some MachXO2 FPGAs, depending on the number of
> LUTs (and the corresponding configuration flash size).
>
> Signed-off-by: Johannes Zink <j.zink@pengutronix.de>
> ---
> drivers/fpga/machxo2-common.c | 28 ++++++++++++++++++++++++++--
> 1 file changed, 26 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/fpga/machxo2-common.c b/drivers/fpga/machxo2-common.c
> index ccf9a50fc590..e8967cdee2c6 100644
> --- a/drivers/fpga/machxo2-common.c
> +++ b/drivers/fpga/machxo2-common.c
> @@ -17,6 +17,8 @@
> #include <linux/module.h>
> #include <linux/of.h>
> #include <linux/property.h>
> +#include <linux/iopoll.h>
> +#include <linux/time.h>
> #include "machxo2-common.h"
>
> #define MACHXO2_LOW_DELAY_USEC 5
> @@ -24,6 +26,8 @@
> #define MACHXO2_REFRESH_USEC 4800
> #define MACHXO2_MAX_BUSY_LOOP 128
> #define MACHXO2_MAX_REFRESH_LOOP 16
> +#define MACHXO2_MAX_ERASE_USEC (30 * USEC_PER_SEC)
> +#define MACHXO2_ERASE_USEC_SLEEP (20 * USEC_PER_MSEC)
>
> #define MACHXO2_PAGE_SIZE 16
> #define MACHXO2_BUF_SIZE (MACHXO2_PAGE_SIZE + 4)
> @@ -54,6 +58,18 @@
> #define ISC_ERASE_FEATURE_ROW BIT(17)
> #define ISC_ERASE_UFM BIT(19)
>
> +static inline int machxo2_wait_until_not_busy_timeout(struct machxo2_common_priv *priv)
> +{
> + int ret, pollret;
> + u32 status = MACHXO2_BUSY;
> +
> + pollret = read_poll_timeout(priv->get_status, ret,
> + (ret && ret != -EAGAIN) || !(status & MACHXO2_BUSY),
> + MACHXO2_ERASE_USEC_SLEEP, MACHXO2_MAX_ERASE_USEC,
> + true, priv, &status);
Why just taking care of erase timeout? I see the busy wait in many
places.
> +
> + return ret ?: pollret;
> +}
>
> static inline u8 get_err(u32 status)
> {
> @@ -114,6 +130,12 @@ static int machxo2_cleanup(struct fpga_manager *mgr)
> if (ret)
> goto fail;
>
> + ret = machxo2_wait_until_not_busy_timeout(priv);
> + if (ret) {
> + dev_err(&mgr->dev, "Erase operation failed (%d)", ret);
> + goto fail;
> + }
> +
> ret = machxo2_wait_until_not_busy(priv);
Is this line still needed?
> if (ret)
> goto fail;
> @@ -192,9 +214,11 @@ static int machxo2_write_init(struct fpga_manager *mgr,
> if (ret)
> goto fail;
>
> - ret = machxo2_wait_until_not_busy(priv);
> - if (ret)
> + ret = machxo2_wait_until_not_busy_timeout(priv);
> + if (ret) {
> + dev_err(&mgr->dev, "Erase operation failed (%d)", ret);
> goto fail;
> + }
>
> priv->get_status(priv, &status);
> if (status & MACHXO2_FAIL) {
> --
> 2.30.2
>
next prev parent reply other threads:[~2022-08-29 9:36 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 14:13 [PATCH 00/16] Add support for Lattice MachXO2 programming via I2C Johannes Zink
2022-08-25 14:13 ` [PATCH 01/16] dt-bindings: fpga: convert Lattice MachXO2 Slave binding to YAML Johannes Zink
2022-08-30 20:30 ` Rob Herring
2022-08-31 7:12 ` Johannes Zink
2022-08-25 14:13 ` [PATCH 02/16] dt-bindings: fpga: machxo2-slave: add erasure properties Johannes Zink
2022-08-29 7:39 ` Xu Yilun
2022-08-30 20:36 ` Rob Herring
2022-08-31 7:07 ` Johannes Zink
2022-08-25 14:13 ` [PATCH 03/16] dt-bindings: fpga: machxo2-slave: add pin for program sequence init Johannes Zink
2022-08-25 18:51 ` Rob Herring
2022-08-26 7:56 ` Johannes Zink
2022-08-29 7:45 ` Xu Yilun
2022-08-25 14:13 ` [PATCH 04/16] dt-bindings: fpga: machxo2-slave: add lattice,machxo2-slave-i2c compatible Johannes Zink
2022-08-30 20:40 ` Rob Herring
2022-08-31 7:10 ` Johannes Zink
2022-08-25 14:13 ` [PATCH 05/16] fpga: machxo2-spi: remove #ifdef DEBUG Johannes Zink
2022-08-25 14:13 ` [PATCH 06/16] fpga: machxo2-spi: factor out status check for readability Johannes Zink
2022-08-25 14:13 ` [PATCH 07/16] fpga: machxo2-spi: fix big-endianness incompatibility Johannes Zink
2022-08-29 8:19 ` Xu Yilun
2022-08-29 10:41 ` Johannes Zink
2022-08-25 14:13 ` [PATCH 08/16] fpga: machxo2-spi: simplify with spi_sync_transfer() Johannes Zink
2022-08-25 14:13 ` [PATCH 09/16] fpga: machxo2-spi: simplify spi write commands Johannes Zink
2022-08-25 14:13 ` [PATCH 10/16] fpga: machxo2-spi: prepare extraction of common code Johannes Zink
2022-08-25 14:13 ` [PATCH 11/16] fpga: machxo2: move non-spi-related functionality to " Johannes Zink
2022-08-25 14:13 ` [PATCH 12/16] fpga: machxo2: improve status register dump Johannes Zink
2022-08-25 14:13 ` [PATCH 13/16] fpga: machxo2: add optional additional flash areas to be erased Johannes Zink
2022-08-25 14:13 ` [PATCH 14/16] fpga: machxo2: add program initialization signalling via gpio Johannes Zink
2022-08-25 14:13 ` [PATCH 15/16] fpga: machxo2: extend erase timeout for machxo2 FPGA Johannes Zink
2022-08-29 9:26 ` Xu Yilun [this message]
2022-08-29 10:51 ` Johannes Zink
2022-08-29 14:57 ` Xu Yilun
2022-08-31 7:56 ` Johannes Zink
2022-08-25 14:13 ` [PATCH 16/16] fpga: machxo2: add configuration over i2c Johannes Zink
2022-08-29 9:47 ` Xu Yilun
2022-08-29 13:21 ` Johannes Zink
2022-08-29 14:45 ` Xu Yilun
2022-08-31 16:07 ` Johannes Zink
2022-08-25 15:25 ` [PATCH 00/16] Add support for Lattice MachXO2 programming via I2C Ivan Bornyakov
2022-08-26 6:32 ` Johannes Zink
2022-08-26 8:15 ` Ivan Bornyakov
2022-08-26 8:25 ` Sascha Hauer
2022-08-26 9:00 ` Ivan Bornyakov
2022-08-26 9:19 ` Ivan Bornyakov
2022-08-26 15:26 ` Xu Yilun
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=YwyGWELZ7WfCE3FS@yilunxu-OptiPlex-7050 \
--to=yilun.xu@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=hao.wu@intel.com \
--cc=j.zink@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-fpga@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=robh+dt@kernel.org \
/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