public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Jon Hunter <jgchunter@gmail.com>,
	Jon Hunter <jonathanh@nvidia.com>,
	linux-omap@vger.kernel.org,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	linux-kernel@vger.kernel.org,
	"aaro.koskinen@iki.fi >> Aaro Koskinen" <aaro.koskinen@iki.fi>,
	tuukka.tikkanen@linaro.org,
	"khilman@deeprootsystems.com >> Kevin Hilman" 
	<khilman@deeprootsystems.com>,
	"linux@arm.linux.org.uk >> Russell King" <linux@arm.linux.org.uk>
Subject: Re: [PATCH] ARM: OMAP1: PM: fix some build warnings on 1510-only Kconfigs
Date: Wed, 11 Feb 2015 12:37:58 -0800	[thread overview]
Message-ID: <20150211203757.GH2531@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1502110218090.3767@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [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

  parent reply	other threads:[~2015-02-11 21:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-07  0:23 [PATCH] ARM: OMAP1: PM: fix some build warnings on 1510-only Kconfigs Paul Walmsley
     [not found] ` <54D9CFBC.3070405@nvidia.com>
2015-02-10 10:57   ` Jon Hunter
2015-02-11  2:25     ` Paul Walmsley
2015-02-11 17:39       ` Jon Hunter
2015-02-11 20:26         ` Tony Lindgren
2015-02-11 20:37       ` Tony Lindgren [this message]
2015-02-11 21:00         ` Paul Walmsley
2015-02-11 21:14           ` Tony Lindgren
2015-02-12 11:26             ` Jon Hunter
2015-02-12 12:34               ` Jon Hunter
2015-03-16 23:13                 ` Tony Lindgren

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=20150211203757.GH2531@atomide.com \
    --to=tony@atomide.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=jgchunter@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=paul@pwsan.com \
    --cc=tuukka.tikkanen@linaro.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