[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <df532fef-1533-9da7-d676-f4671746fde3@gmail.com>
Date: Fri, 20 Mar 2020 17:39:01 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Thierry Reding <thierry.reding@...il.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Rob Herring <robh+dt@...nel.org>,
Jon Hunter <jonathanh@...dia.com>, linux-tegra@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/7] clocksource: Add Tegra186 timers support
20.03.2020 16:34, Thierry Reding пишет:
> From: Thierry Reding <treding@...dia.com>
>
> Currently this only supports a single watchdog, which uses a timer in
> the background for countdown. Eventually the timers could be used for
> various time-keeping tasks, but by default the architected timer will
> already provide that functionality.
>
> Signed-off-by: Thierry Reding <treding@...dia.com>
> ---
> drivers/clocksource/Kconfig | 8 +
> drivers/clocksource/Makefile | 1 +
> drivers/clocksource/timer-tegra186.c | 377 +++++++++++++++++++++++++++
> 3 files changed, 386 insertions(+)
> create mode 100644 drivers/clocksource/timer-tegra186.c
Hello Thierry,
Shouldn't this driver reside in drivers/watchdog/? Like it's done in a
case of the T30+ driver.
...
> +static int __maybe_unused tegra186_timer_suspend(struct device *dev)
> +{
> + return 0;
> +}
> +
> +static int __maybe_unused tegra186_timer_resume(struct device *dev)
> +{
> + return 0;
> +}
> +
> +static SIMPLE_DEV_PM_OPS(tegra186_timer_pm_ops, tegra186_timer_suspend,
> + tegra186_timer_resume);
Perhaps will be better to remove these OPS for now?
Powered by blists - more mailing lists