Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754147AbbBKVIU (ORCPT ); Wed, 11 Feb 2015 16:08:20 -0500 Received: from pmta1.delivery1.ore.mailhop.org ([54.191.214.3]:56105 "EHLO pmta1.delivery1.ore.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754094AbbBKVIR (ORCPT ); Wed, 11 Feb 2015 16:08:17 -0500 X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 104.193.169.186 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX1//tEE1qR7dEOEHUXGemgXx Date: Wed, 11 Feb 2015 12:37:58 -0800 From: Tony Lindgren To: Paul Walmsley Cc: Jon Hunter , Jon Hunter , linux-omap@vger.kernel.org, "linux-arm-kernel@lists.infradead.org" , linux-kernel@vger.kernel.org, "aaro.koskinen@iki.fi >> Aaro Koskinen" , tuukka.tikkanen@linaro.org, "khilman@deeprootsystems.com >> Kevin Hilman" , "linux@arm.linux.org.uk >> Russell King" Subject: Re: [PATCH] ARM: OMAP1: PM: fix some build warnings on 1510-only Kconfigs Message-ID: <20150211203757.GH2531@atomide.com> References: <54D9CFBC.3070405@nvidia.com> <54D9E42C.7010105@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1377 Lines: 31 * Paul Walmsley [150210 18:28]: > On Tue, 10 Feb 2015, Jon Hunter wrote: > > On 07/02/2015 00:23, Paul Walmsley wrote: > > > Unfortunately, there is not a single TRM for the omap5910 but individual > > documents for each chapter in the original TRM. Check out the "OMAP5910 > > Dual-Core Processor Timer Reference Guide" and possibly the "OMAP5910 > > Dual-Core Processor Clock Generation and System Reset Management > > Reference Guide" > > > > The omap15xx/5910 did have a 32k timer but as you can see it appears it > > was never supported by the kernel for this device (not sure why). I do > > recall that there is some errata regarding the 32k timer, if you look at > > the omap5910 errata document and search for 32k you should find it. > > OK thanks for the context. I probably am not going to investigate adding > support for this timer on OMAP1510/5910 - am primarily trying to avoid > causing a regression on the existing platforms. At least I've never seen the 32KiHz timer registers in any 15xx documentation. Jon are you sure you're not mixing up 5910 (15xx) and 5912 (16xx)? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/