From: Michael Shych <michaelsh@mellanox.com>
To: Guenter Roeck <linux@roeck-us.net>,
"wim@linux-watchdog.org" <wim@linux-watchdog.org>,
"andy@infradead.org" <andy@infradead.org>,
"dvhart@infradead.org" <dvhart@infradead.org>
Cc: "linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
Vadim Pasternak <vadimp@mellanox.com>
Subject: RE: [PATCH v2 3/4] watchdog: mlx-wdt: support new watchdog type with longer timeout period
Date: Sun, 3 May 2020 05:32:58 +0000 [thread overview]
Message-ID: <AM6PR05MB61684CC5C2F65DD790B80849D9A90@AM6PR05MB6168.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <2a055ba3-0602-4e45-2155-521c9514f909@roeck-us.net>
> -----Original Message-----
> From: Guenter Roeck <groeck7@gmail.com> On Behalf Of Guenter Roeck
> Sent: Wednesday, April 29, 2020 3:30 PM
> To: Michael Shych <michaelsh@mellanox.com>; wim@linux-watchdog.org;
> andy@infradead.org; dvhart@infradead.org
> Cc: linux-watchdog@vger.kernel.org; platform-driver-x86@vger.kernel.org;
> Vadim Pasternak <vadimp@mellanox.com>
> Subject: Re: [PATCH v2 3/4] watchdog: mlx-wdt: support new watchdog type
> with longer timeout period
>
> On 4/28/20 6:08 AM, michaelsh@mellanox.com wrote:
> > From: Michael Shych <michaelsh@mellanox.com>
> >
> > New programmable logic device can have watchdog type 3 implementation.
> > It's same as Type 2 with extended maximum timeout period.
> > Maximum timeout is up-to 65535 sec.
> > Type 3 HW watchdog implementation can exist on all Mellanox systems.
> > It is differentiated by WD capability bit.
> >
> > Signed-off-by: Michael Shych <michaelsh@mellanox.com>
> > Reviewed-by: Vadim Pasternak <vadimp@mellanox.com>
> > ---
> > v1-v2:
> > Make changes pointed out by Guenter:
> > -Simplify bit operations
> > -Consistency in registers access
> > -Don't check irrelevant return code
> > ---
> > drivers/watchdog/mlx_wdt.c | 75
> +++++++++++++++++++++++++++++++++++++++-------
> > 1 file changed, 64 insertions(+), 11 deletions(-)
> >
> > diff --git a/drivers/watchdog/mlx_wdt.c b/drivers/watchdog/mlx_wdt.c
> > index 03b9ac4b99af..4e76d4a1af5c 100644
> > --- a/drivers/watchdog/mlx_wdt.c
> > +++ b/drivers/watchdog/mlx_wdt.c
> > @@ -21,6 +21,7 @@
> > #define MLXREG_WDT_CLOCK_SCALE 1000
> > #define MLXREG_WDT_MAX_TIMEOUT_TYPE1 32
> > #define MLXREG_WDT_MAX_TIMEOUT_TYPE2 255
> > +#define MLXREG_WDT_MAX_TIMEOUT_TYPE3 65535
> > #define MLXREG_WDT_MIN_TIMEOUT 1
> > #define MLXREG_WDT_OPTIONS_BASE (WDIOF_KEEPALIVEPING |
> WDIOF_MAGICCLOSE | \
> > WDIOF_SETTIMEOUT)
> > @@ -49,6 +50,7 @@ struct mlxreg_wdt {
> > int tleft_idx;
> > int ping_idx;
> > int reset_idx;
> > + int regmap_val_sz;
> > enum mlxreg_wdt_type wdt_type;
> > };
> >
> > @@ -111,7 +113,8 @@ static int mlxreg_wdt_set_timeout(struct
> watchdog_device *wdd,
> > u32 regval, set_time, hw_timeout;
> > int rc;
> >
> > - if (wdt->wdt_type == MLX_WDT_TYPE1) {
> > + switch (wdt->wdt_type) {
> > + case MLX_WDT_TYPE1:
> > rc = regmap_read(wdt->regmap, reg_data->reg, ®val);
> > if (rc)
> > return rc;
> > @@ -120,14 +123,33 @@ static int mlxreg_wdt_set_timeout(struct
> watchdog_device *wdd,
> > regval = (regval & reg_data->mask) | hw_timeout;
> > /* Rowndown to actual closest number of sec. */
> > set_time = BIT(hw_timeout) / MLXREG_WDT_CLOCK_SCALE;
> > - } else {
> > + rc = regmap_write(wdt->regmap, reg_data->reg, regval);
> > + break;
> > + case MLX_WDT_TYPE2:
> > + set_time = timeout;
> > + rc = regmap_write(wdt->regmap, reg_data->reg, timeout);
> > + break;
> > + case MLX_WDT_TYPE3:
> > + /* WD_TYPE3 has 2B set time register */
> > set_time = timeout;
> > - regval = timeout;
> > + if (wdt->regmap_val_sz == 1) {
> > + timeout = cpu_to_le16(timeout);
> > + regval = timeout & 0xff;
> > + rc = regmap_write(wdt->regmap, reg_data->reg, regval);
> > + if (!rc) {
> > + regval = (timeout & 0xff00) >> 8;
> > + rc = regmap_write(wdt->regmap,
> > + reg_data->reg + 1, regval);
> > + }
> > + } else {
> > + rc = regmap_write(wdt->regmap, reg_data->reg,
> timeout);
> > + }
> > + break;
> > + default:
> > + return -EINVAL;
> > }
> >
> > wdd->timeout = set_time;
> > - rc = regmap_write(wdt->regmap, reg_data->reg, regval);
> > -
> > if (!rc) {
> > /*
> > * Restart watchdog with new timeout period
> > @@ -147,10 +169,26 @@ static unsigned int mlxreg_wdt_get_timeleft(struct
> watchdog_device *wdd)
> > {
> > struct mlxreg_wdt *wdt = watchdog_get_drvdata(wdd);
> > struct mlxreg_core_data *reg_data = &wdt->pdata->data[wdt-
> >tleft_idx];
> > - u32 regval;
> > + u32 regval, msb, lsb;
> > int rc;
> >
> > - rc = regmap_read(wdt->regmap, reg_data->reg, ®val);
> > + if (wdt->wdt_type == MLX_WDT_TYPE2) {
> > + rc = regmap_read(wdt->regmap, reg_data->reg, ®val);
> > + } else {
> > + /* WD_TYPE3 has 2 byte timeleft register */
> > + if (wdt->regmap_val_sz == 1) {
> > + rc = regmap_read(wdt->regmap, reg_data->reg, &lsb);
> > + if (!rc) {
> > + rc = regmap_read(wdt->regmap,
> > + reg_data->reg + 1, &msb);
> > + regval = (msb & 0xff) << 8 | (lsb & 0xff);
> > + regval = le16_to_cpu(regval);
>
> I don't think my concerns regarding the use of le16_to_cpu() have been
> addressed, and I still think this results in bad data on a big endian
> system.
>
> Guenter
You are right. These are unnecessary conversions. I removed them as well as reference
To them in the document. Resending patchset v3.
>
> > + }
> > + } else {
> > + rc = regmap_read(wdt->regmap, reg_data->reg,
> ®val);
> > + }
> > + }
> > +
> > /* Return 0 timeleft in case of failure register read. */
> > return rc == 0 ? regval : 0;
> > }
> > @@ -212,13 +250,23 @@ static void mlxreg_wdt_config(struct mlxreg_wdt
> *wdt,
> > wdt->wdd.info = &mlxreg_wdt_aux_info;
> >
> > wdt->wdt_type = pdata->version;
> > - if (wdt->wdt_type == MLX_WDT_TYPE2) {
> > - wdt->wdd.ops = &mlxreg_wdt_ops_type2;
> > - wdt->wdd.max_timeout =
> MLXREG_WDT_MAX_TIMEOUT_TYPE2;
> > - } else {
> > + switch (wdt->wdt_type) {
> > + case MLX_WDT_TYPE1:
> > wdt->wdd.ops = &mlxreg_wdt_ops_type1;
> > wdt->wdd.max_timeout =
> MLXREG_WDT_MAX_TIMEOUT_TYPE1;
> > + break;
> > + case MLX_WDT_TYPE2:
> > + wdt->wdd.ops = &mlxreg_wdt_ops_type2;
> > + wdt->wdd.max_timeout =
> MLXREG_WDT_MAX_TIMEOUT_TYPE2;
> > + break;
> > + case MLX_WDT_TYPE3:
> > + wdt->wdd.ops = &mlxreg_wdt_ops_type2;
> > + wdt->wdd.max_timeout =
> MLXREG_WDT_MAX_TIMEOUT_TYPE3;
> > + break;
> > + default:
> > + break;
> > }
> > +
> > wdt->wdd.min_timeout = MLXREG_WDT_MIN_TIMEOUT;
> > }
> >
> > @@ -249,6 +297,11 @@ static int mlxreg_wdt_probe(struct platform_device
> *pdev)
> >
> > wdt->wdd.parent = dev;
> > wdt->regmap = pdata->regmap;
> > + rc = regmap_get_val_bytes(wdt->regmap);
> > + if (rc < 0)
> > + return -EINVAL;
> > +
> > + wdt->regmap_val_sz = rc;
> > mlxreg_wdt_config(wdt, pdata);
> >
> > if ((pdata->features & MLXREG_CORE_WD_FEATURE_NOWAYOUT))
> >
next prev parent reply other threads:[~2020-05-03 5:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 13:08 [PATCH v2 0/4] support watchdog with longer timeout period michaelsh
2020-04-28 13:08 ` [PATCH v2 1/4] platform_data/mlxreg: support new watchdog type " michaelsh
2020-04-28 13:08 ` [PATCH v2 2/4] platform/x86: mlx-platform: support new watchdog type with longer timeout michaelsh
2020-04-28 13:08 ` [PATCH v2 3/4] watchdog: mlx-wdt: support new watchdog type with longer timeout period michaelsh
2020-04-29 12:29 ` Guenter Roeck
2020-05-03 5:32 ` Michael Shych [this message]
2020-04-28 13:08 ` [PATCH v2 4/4] docs: watchdog: mlx-wdt: Add description of new watchdog type 3 michaelsh
2020-04-28 15:36 ` [PATCH v2 0/4] support watchdog with longer timeout period Andy Shevchenko
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=AM6PR05MB61684CC5C2F65DD790B80849D9A90@AM6PR05MB6168.eurprd05.prod.outlook.com \
--to=michaelsh@mellanox.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vadimp@mellanox.com \
--cc=wim@linux-watchdog.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;
as well as URLs for NNTP newsgroup(s).