devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bharat Bhushan <bbhushan2@marvell.com>,
	wim@linux-watchdog.org, linux@roeck-us.net, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org,
	linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2 v5] Watchdog: Add marvell GTI watchdog driver
Date: Thu, 4 May 2023 08:56:39 +0200	[thread overview]
Message-ID: <9ac282d5-9b37-dae9-2cb6-824dc50b2183@linaro.org> (raw)
In-Reply-To: <20230503121016.6093-2-bbhushan2@marvell.com>

On 03/05/2023 14:10, Bharat Bhushan wrote:
> This patch add support for Marvell GTI watchdog.  Global timer
> unit (GTI) support hardware watchdog timer. Software programs
> watchdog timer to generate interrupt on first timeout, second
> timeout is configured to be ignored and system reboots on
> third timeout.
> 
> Signed-off-by: Bharat Bhushan <bbhushan2@marvell.com>



> +
> +static void gti_clk_disable_unprepare(void *data)
> +{
> +	clk_disable_unprepare(data);
> +}
> +
> +static int gti_wdt_get_cntfrq(struct platform_device *pdev,
> +			      struct gti_wdt_priv *priv)
> +{
> +	int err;
> +
> +	priv->sclk = devm_clk_get(&pdev->dev, NULL);
> +	if (IS_ERR(priv->sclk))
> +		return PTR_ERR(priv->sclk);

NAK. Undocumented property. Test your DTS. There is no way it was
working. Either you did not test DTS against bindings or you did not
test driver and DTS together.

Better actually to upstream your DTS...

Best regards,
Krzysztof


  reply	other threads:[~2023-05-04  6:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <linux-kernel@vger.kernel.org, sgoutham@marvell.com>
2023-05-03 12:10 ` [PATCH 1/2 v5] dt-bindings: watchdog: marvell GTI system watchdog driver Bharat Bhushan
2023-05-03 12:10   ` [PATCH 2/2 v5] Watchdog: Add marvell GTI " Bharat Bhushan
2023-05-04  6:56     ` Krzysztof Kozlowski [this message]
2023-05-04  6:54   ` [PATCH 1/2 v5] dt-bindings: watchdog: marvell GTI system " Krzysztof Kozlowski
2023-05-04  9:02     ` [EXT] " Bharat Bhushan
2023-05-04 11:07       ` Krzysztof Kozlowski
2023-05-04 17:10         ` Bharat Bhushan
2023-05-05  6:38           ` Krzysztof Kozlowski
2023-05-05  7:17             ` Bharat Bhushan
2023-05-05 10:31               ` Krzysztof Kozlowski
2023-05-05  7:55             ` Bharat Bhushan
2023-05-05 10:33               ` Krzysztof Kozlowski
2023-05-05 10:41                 ` Bharat Bhushan
2023-05-05 10:57                   ` Krzysztof Kozlowski
2023-05-05 11:15                     ` Bharat Bhushan
2023-05-05 11:57                       ` Krzysztof Kozlowski
2023-05-05 12:19                         ` Bharat Bhushan
2023-05-05 12:26                           ` Krzysztof Kozlowski

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=9ac282d5-9b37-dae9-2cb6-824dc50b2183@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=bbhushan2@marvell.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=robh+dt@kernel.org \
    --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).