From: Tom Rix <trix@redhat.com>
To: Russ Weight <russell.h.weight@intel.com>,
mdf@kernel.org, linux-fpga@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: lgoncalv@redhat.com, yilun.xu@intel.com, hao.wu@intel.com,
matthew.gerlach@intel.com
Subject: Re: [PATCH v1 2/2] fpga: dfl: fme: Clear fme global errors at driver init
Date: Wed, 20 Oct 2021 05:59:47 -0700 [thread overview]
Message-ID: <0b911b70-1cea-2d9e-1dfa-d1c743eae396@redhat.com> (raw)
In-Reply-To: <20211019231545.47118-3-russell.h.weight@intel.com>
On 10/19/21 4:15 PM, Russ Weight wrote:
> When the fme-error driver initializes, log any pre-existing errors and
> clear them. To avoid code replication, common code is gathered into
> a common fme_err_clear() function and a structure (err_reg) is created
> to describe each of the error registers, the corresponding mask
> registers, and the default mask for each register.
>
> Signed-off-by: Russ Weight <russell.h.weight@intel.com>
> ---
> drivers/fpga/dfl-fme-error.c | 128 +++++++++++++++++++++++------------
> 1 file changed, 84 insertions(+), 44 deletions(-)
>
> diff --git a/drivers/fpga/dfl-fme-error.c b/drivers/fpga/dfl-fme-error.c
> index 51c2892ec06d..44da7b30c469 100644
> --- a/drivers/fpga/dfl-fme-error.c
> +++ b/drivers/fpga/dfl-fme-error.c
> @@ -39,6 +39,27 @@
>
> #define ERROR_MASK GENMASK_ULL(63, 0)
>
> +struct err_reg {
> + char *name;
> + u32 err_offset;
> + u32 mask_offset;
> + u32 mask_value;
> +};
> +
> +static struct err_reg pcie0_reg = {
> + .name = "PCIE0",
> + .err_offset = PCIE0_ERROR,
> + .mask_offset = PCIE0_ERROR_MASK,
> + .mask_value = 0ULL
> +};
> +
> +static struct err_reg pcie1_reg = {
> + .name = "PCIE1",
> + .err_offset = PCIE1_ERROR,
> + .mask_offset = PCIE1_ERROR_MASK,
> + .mask_value = 0ULL
> +};
> +
Can these be stored in an array ?
> static ssize_t pcie0_errors_show(struct device *dev,
> struct device_attribute *attr, char *buf)
> {
> @@ -55,31 +76,48 @@ static ssize_t pcie0_errors_show(struct device *dev,
> return sprintf(buf, "0x%llx\n", (unsigned long long)value);
> }
>
> -static ssize_t pcie0_errors_store(struct device *dev,
> - struct device_attribute *attr,
> - const char *buf, size_t count)
> +static int fme_err_clear(struct device *dev, struct err_reg *reg,
> + u64 err, bool clear_all)
> {
> struct dfl_feature_platform_data *pdata = dev_get_platdata(dev);
> void __iomem *base;
> int ret = 0;
> - u64 v, val;
> -
> - if (kstrtou64(buf, 0, &val))
> - return -EINVAL;
> + u64 v;
>
> base = dfl_get_feature_ioaddr_by_id(dev, FME_FEATURE_ID_GLOBAL_ERR);
>
> mutex_lock(&pdata->lock);
> - writeq(GENMASK_ULL(63, 0), base + PCIE0_ERROR_MASK);
> + writeq(GENMASK_ULL(63, 0), base + reg->mask_offset);
>
> - v = readq(base + PCIE0_ERROR);
> - if (val == v)
> - writeq(v, base + PCIE0_ERROR);
> - else
> + v = readq(base + reg->err_offset);
> + if (clear_all || err == v) {
> + if (clear_all && v)
clear_all will over report.
> + dev_warn(dev, "%s: %s Errors: 0x%llx\n",
> + __func__, reg->name, v);
> +
> + writeq(v, base + reg->err_offset);
> + } else {
> ret = -EINVAL;
> + }
>
> - writeq(0ULL, base + PCIE0_ERROR_MASK);
> + writeq(reg->mask_value, base + reg->mask_offset);
> mutex_unlock(&pdata->lock);
> +
> + return ret;
> +}
> +
> +static ssize_t pcie0_errors_store(struct device *dev,
> + struct device_attribute *attr,
> + const char *buf, size_t count)
> +{
> + u64 val;
> + int ret;
> +
> + if (kstrtou64(buf, 0, &val))
> + return -EINVAL;
> +
> + ret = fme_err_clear(dev, &pcie0_reg, val, false);
> +
> return ret ? ret : count;
> }
> static DEVICE_ATTR_RW(pcie0_errors);
> @@ -104,27 +142,14 @@ static ssize_t pcie1_errors_store(struct device *dev,
> struct device_attribute *attr,
> const char *buf, size_t count)
> {
This looks like a copy of pcie0_errors_store can these functions be
consolidated ?
> - struct dfl_feature_platform_data *pdata = dev_get_platdata(dev);
> - void __iomem *base;
> - int ret = 0;
> - u64 v, val;
> + u64 val;
> + int ret;
>
> if (kstrtou64(buf, 0, &val))
> return -EINVAL;
>
> - base = dfl_get_feature_ioaddr_by_id(dev, FME_FEATURE_ID_GLOBAL_ERR);
> + ret = fme_err_clear(dev, &pcie1_reg, val, false);
>
> - mutex_lock(&pdata->lock);
> - writeq(GENMASK_ULL(63, 0), base + PCIE1_ERROR_MASK);
> -
> - v = readq(base + PCIE1_ERROR);
> - if (val == v)
> - writeq(v, base + PCIE1_ERROR);
> - else
> - ret = -EINVAL;
> -
> - writeq(0ULL, base + PCIE1_ERROR_MASK);
> - mutex_unlock(&pdata->lock);
> return ret ? ret : count;
> }
> static DEVICE_ATTR_RW(pcie1_errors);
> @@ -218,29 +243,26 @@ static ssize_t fme_errors_store(struct device *dev,
> struct device_attribute *attr,
> const char *buf, size_t count)
> {
> - struct dfl_feature_platform_data *pdata = dev_get_platdata(dev);
> + static struct err_reg fme_reg = {
> + .name = "FME",
> + .err_offset = FME_ERROR,
> + .mask_offset = FME_ERROR_MASK,
> + .mask_value = 0ULL
> + };
> void __iomem *base;
> - u64 v, val;
> - int ret = 0;
> + u64 val;
> + int ret;
>
> if (kstrtou64(buf, 0, &val))
> return -EINVAL;
>
> + /* Workaround: disable MBP_ERROR if feature revision is 0 */
> base = dfl_get_feature_ioaddr_by_id(dev, FME_FEATURE_ID_GLOBAL_ERR);
> + if (!dfl_feature_revision(base))
> + fme_reg.mask_value = MBP_ERROR;
>
> - mutex_lock(&pdata->lock);
> - writeq(GENMASK_ULL(63, 0), base + FME_ERROR_MASK);
> + ret = fme_err_clear(dev, &fme_reg, val, false);
>
> - v = readq(base + FME_ERROR);
> - if (val == v)
> - writeq(v, base + FME_ERROR);
> - else
> - ret = -EINVAL;
> -
> - /* Workaround: disable MBP_ERROR if feature revision is 0 */
> - writeq(dfl_feature_revision(base) ? 0ULL : MBP_ERROR,
> - base + FME_ERROR_MASK);
> - mutex_unlock(&pdata->lock);
> return ret ? ret : count;
> }
> static DEVICE_ATTR_RW(fme_errors);
> @@ -338,6 +360,24 @@ static void fme_err_mask(struct device *dev, bool mask)
> static int fme_global_err_init(struct platform_device *pdev,
> struct dfl_feature *feature)
> {
> + static struct err_reg fme_reg = {
> + .name = "FME",
> + .err_offset = FME_ERROR,
> + .mask_offset = FME_ERROR_MASK,
> + .mask_value = 0ULL
> + };
> + void __iomem *base;
> +
> + /* Workaround: disable MBP_ERROR if feature revision is 0 */
> + base = dfl_get_feature_ioaddr_by_id(&pdev->dev,
> + FME_FEATURE_ID_GLOBAL_ERR);
> + if (!dfl_feature_revision(base))
> + fme_reg.mask_value = MBP_ERROR;
A similar block above to set fme_reg.mask_value.
These should be consolidated.
> +
> + (void)fme_err_clear(&pdev->dev, &pcie0_reg, 0ULL, true);
remove casting return to (void)
Tom
> + (void)fme_err_clear(&pdev->dev, &pcie1_reg, 0ULL, true);
> + (void)fme_err_clear(&pdev->dev, &fme_reg, 0ULL, true);
> +
> fme_err_mask(&pdev->dev, false);
>
> return 0;
next prev parent reply other threads:[~2021-10-20 13:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 23:15 [PATCH v1 0/2] fpga: dfl: Log and clear errors on driver init Russ Weight
2021-10-19 23:15 ` [PATCH v1 1/2] fpga: dfl: afu: Clear port errors in afu init Russ Weight
2021-10-20 4:15 ` Xu Yilun
2021-10-20 12:18 ` Tom Rix
2021-10-20 16:02 ` Russ Weight
2021-10-19 23:15 ` [PATCH v1 2/2] fpga: dfl: fme: Clear fme global errors at driver init Russ Weight
2021-10-20 12:59 ` Tom Rix [this message]
2021-10-20 4:44 ` [PATCH v1 0/2] fpga: dfl: Log and clear errors on " Wu, Hao
2021-10-21 0:05 ` Russ Weight
2021-10-21 0:43 ` Wu, Hao
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=0b911b70-1cea-2d9e-1dfa-d1c743eae396@redhat.com \
--to=trix@redhat.com \
--cc=hao.wu@intel.com \
--cc=lgoncalv@redhat.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.gerlach@intel.com \
--cc=mdf@kernel.org \
--cc=russell.h.weight@intel.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).