From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Maarten Lankhorst <dev-FcfepWsj2zOByvU0x3ry2g@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] arm/tegra: Enable watchdog support for tegra114 and tegra124.
Date: Fri, 12 Feb 2016 18:28:10 +0100 [thread overview]
Message-ID: <20160212172810.GB29081@ulmo> (raw)
In-Reply-To: <564AFE51.6060601-FcfepWsj2zOByvU0x3ry2g@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
On Tue, Nov 17, 2015 at 11:15:45AM +0100, Maarten Lankhorst wrote:
> This allows the watchdog timer to work on my tegra124.
>
> tegra_wdt specifies: compatible = "nvidia,tegra30-timer";
>
> But the dtsi was only setting tegra20-timer, fix this
> by adding tegra30-timer explicitly. This allows
> the watchdog to work on my Jetson TK1.
>
> Signed-off-by: Maarten Lankhorst <dev-FcfepWsj2zOByvU0x3ry2g@public.gmane.org>
> ---
> XXX: Should this be Cc: stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org to add the missing device on older kernels?
I've applied this with a slightly reworded commit message. I haven't
added a Cc: stable because I don't think this qualifies. There is no
regression that this fixes, or any bugs. It enables a feature, which
is useful, but doesn't need to go to stable in my opinion.
If you or anyone else feels strongly I can be convinced to add it,
though.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-02-12 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 10:15 [PATCH] arm/tegra: Enable watchdog support for tegra114 and tegra124 Maarten Lankhorst
[not found] ` <564AFE51.6060601-FcfepWsj2zOByvU0x3ry2g@public.gmane.org>
2016-02-12 17:28 ` Thierry Reding [this message]
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=20160212172810.GB29081@ulmo \
--to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dev-FcfepWsj2zOByvU0x3ry2g@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).