From: "Łukasz Majewski" <lukma@nabladev.com>
To: Thierry Reding <treding@nvidia.com>,
Svyatoslav Ryhel <clamor95@gmail.com>
Cc: Tom Rini <trini@konsulko.com>, u-boot@lists.denx.de
Subject: Re: [PATCH 1/2] timer: tegra: Bind watchdog driver when timer node is processed
Date: Wed, 17 Sep 2025 14:46:04 +0200 [thread overview]
Message-ID: <20250917144604.49f792b4@wsk> (raw)
In-Reply-To: <20250826093936.3521235-1-lukma@nabladev.com>
Dear Community,
> The Tegra30 SoC is a bit special, as it doesn't have the separate IP
> block to provide watchdog functionality.
>
> Instead, timer IP block allows such functionality when properly
> configured.
>
> As in the tegra30.dtsi there is a timer node, which "covers" all
> timers, with 'nvidia,tegra30-timer' compatibility it was necessary to
> manually bind U-Boot's WDT driver (based on WDT_UCLASS).
>
> Signed-off-by: Lukasz Majewski <lukma@nabladev.com>
> ---
> drivers/timer/tegra-timer.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/drivers/timer/tegra-timer.c b/drivers/timer/tegra-timer.c
> index 3545424889d..361539efa43 100644
> --- a/drivers/timer/tegra-timer.c
> +++ b/drivers/timer/tegra-timer.c
> @@ -11,6 +11,8 @@
> #include <asm/arch/clock.h>
> #include <asm/arch/tegra.h>
>
> +#include <dm/lists.h>
> +
> #define TEGRA_OSC_CLK_ENB_L_SET (NV_PA_CLK_RST_BASE +
> 0x320) #define TEGRA_OSC_SET_CLK_ENB_TMR BIT(5)
>
> @@ -106,6 +108,21 @@ static int tegra_timer_probe(struct udevice *dev)
> return 0;
> }
>
> +static int tegra_timer_bind(struct udevice *dev)
> +{
> + /*
> + * In Tegra 30 SoC the Watchdog is accomplished
> + * by the timer IP block (timer5).
> + */
> + if (CONFIG_IS_ENABLED(WDT_TEGRA))
> + return device_bind_driver_to_node(dev, "tegra_wdt",
> + "tegra-wdt",
> + dev_ofnode(dev),
> + NULL);
> +
> + return 0;
> +}
> +
> static const struct timer_ops tegra_timer_ops = {
> .get_count = tegra_timer_get_count,
> };
> @@ -124,6 +141,7 @@ U_BOOT_DRIVER(tegra_timer) = {
> .id = UCLASS_TIMER,
> .of_match = tegra_timer_ids,
> .probe = tegra_timer_probe,
> + .bind = tegra_timer_bind,
> .ops = &tegra_timer_ops,
> .flags = DM_FLAG_PRE_RELOC,
> };
Are there any new comments regarding this patch set?
--
Best regards,
Lukasz Majewski
--
Nabla Software Engineering GmbH
HRB 40522 Augsburg
Phone: +49 821 45592596
E-Mail: office@nabladev.com
Geschftsfhrer : Stefano Babic
next prev parent reply other threads:[~2025-09-17 12:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 9:39 [PATCH 1/2] timer: tegra: Bind watchdog driver when timer node is processed Lukasz Majewski
2025-08-26 9:39 ` [PATCH 2/2] watchdog: Add implementation of NVIDIA's Tegra 30 watchdog driver Lukasz Majewski
2025-09-17 14:01 ` Svyatoslav Ryhel
2025-08-26 10:10 ` [PATCH 1/2] timer: tegra: Bind watchdog driver when timer node is processed Svyatoslav Ryhel
2025-09-08 12:41 ` Łukasz Majewski
2025-09-08 13:55 ` Svyatoslav Ryhel
2025-09-09 10:15 ` Łukasz Majewski
2025-09-09 11:26 ` Svyatoslav Ryhel
2025-09-09 15:39 ` Tom Rini
2025-09-09 15:44 ` Svyatoslav Ryhel
2025-09-09 15:47 ` Tom Rini
2025-09-09 16:08 ` Svyatoslav Ryhel
2025-09-10 8:51 ` Francesco Dolcini
2025-09-10 12:28 ` Łukasz Majewski
2025-09-10 14:07 ` Francesco Dolcini
2025-09-11 6:46 ` Łukasz Majewski
2025-09-10 6:52 ` Łukasz Majewski
2025-09-17 12:46 ` Łukasz Majewski [this message]
2025-09-17 13:40 ` Svyatoslav Ryhel
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=20250917144604.49f792b4@wsk \
--to=lukma@nabladev.com \
--cc=clamor95@gmail.com \
--cc=treding@nvidia.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.