From: Krzysztof Kozlowski <krzk@kernel.org>
To: Artur Kowalski <arturkow2000@gmail.com>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Thomas Gleixner <tglx@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-watchdog@vger.kernel.org, linux-doc@vger.kernel.org,
clamor95@gmail.com
Subject: Re: [PATCH 3/6] watchdog: tegra_wdt: Support Tegra20
Date: Tue, 10 Nov 2026 17:21:27 +0100 [thread overview]
Message-ID: <eb9fdef7-2cef-425b-a62e-c28b7dbe1596@kernel.org> (raw)
In-Reply-To: <20261110-t20-for-upstream-v1-3-5923449951fe@gmail.com>
On 10/11/2026 13:39, Artur Kowalski wrote:
> +static int tegra20_wdt_init(struct platform_device *pdev, struct tegra_wdt *wdt,
> + void __iomem *regs)
> +{
> + struct device *dev = &pdev->dev;
> + struct device_node *np;
> + struct resource res;
> + int ret;
> +
> + /*
> + * RST_SOURCE belongs to the clock and reset controller, whose driver
> + * doesn't use it. Map only this register, without requesting it, as
> + * the region belongs to the clock and reset controller.
> + */
> + np = of_find_compatible_node(NULL, NULL, "nvidia,tegra20-car");
> + if (!np)
> + return dev_err_probe(dev, -ENODEV,
> + "clock and reset controller not found\n");
> +
> + ret = of_address_to_resource(np, 0, &res);
> + of_node_put(np);
> + if (ret)
Looks like doing syscon here. This in general is more fragile.
...
> +/*
> + * Tegra30 and later list "nvidia,tegra20-timer" as well, but match their more
> + * specific compatible string.
> + */
> static const struct of_device_id tegra_wdt_of_match[] = {
> { .compatible = "nvidia,tegra30-timer", .data = &tegra30_wdt_soc },
> + { .compatible = "nvidia,tegra20-timer", .data = &tegra20_wdt_soc },
Why in reversed order?
> { },
> };
> MODULE_DEVICE_TABLE(of, tegra_wdt_of_match);
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-11-10 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 12:39 [PATCH 0/6] watchdog: tegra_wdt: Add Tegra20 support Artur Kowalski
2026-11-10 12:39 ` [PATCH 1/6] clocksource/drivers/timer-tegra: Keep Tegra20's watchdog timers free Artur Kowalski
2026-11-10 12:39 ` [PATCH 2/6] watchdog: tegra_wdt: Move SoC specific parts into match data Artur Kowalski
2026-11-10 12:39 ` [PATCH 3/6] watchdog: tegra_wdt: Support Tegra20 Artur Kowalski
2026-11-10 16:21 ` Krzysztof Kozlowski [this message]
2026-11-10 12:39 ` [PATCH 4/6] soc/tegra: pmc: Add an option to keep the VDE partition on Artur Kowalski
2026-11-10 12:39 ` [PATCH 5/6] soc/tegra: pmc: Add a partition power off notifier Artur Kowalski
2026-11-10 12:39 ` [PATCH 6/6] watchdog: tegra_wdt: Stop on Tegra20 VDE power off Artur Kowalski
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=eb9fdef7-2cef-425b-a62e-c28b7dbe1596@kernel.org \
--to=krzk@kernel.org \
--cc=arturkow2000@gmail.com \
--cc=clamor95@gmail.com \
--cc=corbet@lwn.net \
--cc=daniel.lezcano@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=p.zabel@pengutronix.de \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=tglx@kernel.org \
--cc=thierry.reding@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
all inboxes | Powered by JetHome®