From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: [PATCH v1] ARM: tegra: add nvidia,wdt-timer-id optional property Date: Mon, 03 Feb 2014 14:09:52 -0700 Message-ID: <52F005A0.4080807@wwwdotorg.org> References: <1391204811-6293-1-git-send-email-achew@nvidia.com> <20140203171053.GA28338@e106331-lin.cambridge.arm.com> <643E69AA4436674C8F39DCC2C05F763863199852CA@HQMAIL03.nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <643E69AA4436674C8F39DCC2C05F763863199852CA-lR+7xdUAJVNDw2glCA4ptUEOCMrvLtNR@public.gmane.org> Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Andrew Chew , Mark Rutland Cc: "robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org" , Pawel Moll , "ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org" , "galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org" , "rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org" , "thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" , "abrestic-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org" , "dgreid-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org" , "katierh-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org" , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: linux-tegra@vger.kernel.org On 02/03/2014 11:59 AM, Andrew Chew wrote: >> On Fri, Jan 31, 2014 at 09:46:51PM +0000, Andrew Chew wrote: >>> This optional property can be used to specify which timers are to be >>> used for hardware watchdog timeouts (via a tegra wdt driver). >> >> Is there any reason that a particular timer should be used? > > I worry about colliding with other timer allocations, and wanted to be > flexible in this regard. Are the other timer allocations represented in DT, or simply made by or hard-coded in the driver? If the former, this property seems like a good equivalent of any existing allocations. If the latter, can't the driver just allocate or hard-code the allocation in the same way as any existing allocations?