From: Thierry Reding <thierry.reding@avionic-design.de>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "Terje Bergström" <tbergstrom@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: tegra: Add Tegra20 host1x support
Date: Wed, 14 Nov 2012 21:21:54 +0100 [thread overview]
Message-ID: <20121114202154.GA10742@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <50A3FBFA.3080008@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
On Wed, Nov 14, 2012 at 01:15:54PM -0700, Stephen Warren wrote:
> On 11/14/2012 01:04 PM, Thierry Reding wrote:
> ...
> > According to tegra20_clocks_data.c, the maximum clock frequency
> > for host1x is 166 MHz, so 216 is probably not a good idea. 150 MHz
> > sounds sensible, though.
>
> As a general rule, I wouldn't rely on the upstream clock driver to
> specify accurate maximum clock rates at the moment. Our downstream
> kernel is more likely to be accurate. Still, upstream might be correct
> here already...
I just checked and the downstream kernel has the same maximum clock rate
for host1x.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-14 20:22 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 13:20 [PATCH 0/2] Device tree updates for " Thierry Reding
2012-11-09 13:20 ` [PATCH 1/2] ARM: tegra: Add Tegra20 " Thierry Reding
2012-11-12 9:39 ` Mark Zhang
2012-11-13 4:38 ` Mark Zhang
2012-11-13 6:41 ` Thierry Reding
2012-11-13 7:37 ` Mark Zhang
2012-11-13 7:45 ` Mark Zhang
2012-11-13 7:52 ` Thierry Reding
2012-11-13 8:00 ` Mark Zhang
2012-11-13 8:04 ` Thierry Reding
2012-11-13 8:29 ` Mark Zhang
2012-11-14 8:35 ` Terje Bergström
2012-11-14 8:49 ` Thierry Reding
2012-11-14 10:23 ` Terje Bergström
2012-11-14 10:54 ` Thierry Reding
2012-11-14 16:19 ` Stephen Warren
2012-11-14 16:45 ` Terje Bergström
2012-11-14 18:12 ` Stephen Warren
2012-11-14 20:04 ` Thierry Reding
2012-11-14 20:15 ` Stephen Warren
2012-11-14 20:21 ` Thierry Reding [this message]
2012-11-15 6:56 ` Terje Bergström
2012-11-15 7:11 ` Thierry Reding
2012-11-14 15:01 ` Thierry Reding
2012-11-14 15:29 ` Terje Bergström
2012-11-14 15:33 ` Thierry Reding
2012-11-09 13:20 ` [PATCH 2/2] ARM: tegra: Add Tegra30 " Thierry Reding
2012-11-13 4:37 ` Mark Zhang
2012-11-13 7:45 ` Mark Zhang
2012-11-13 7:53 ` Thierry Reding
2012-11-09 17:34 ` [PATCH 0/2] Device tree updates for " Stephen Warren
2012-11-09 18:44 ` Thierry Reding
2012-11-09 21:10 ` Stephen Warren
2012-11-15 8:21 ` Prashant Gaikwad
2012-11-15 8:50 ` Thierry Reding
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=20121114202154.GA10742@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=tbergstrom@nvidia.com \
/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
Powered by JetHome