linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Terje Bergström" <tbergstrom@nvidia.com>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	"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 10:35:31 +0200	[thread overview]
Message-ID: <50A357D3.9080002@nvidia.com> (raw)
In-Reply-To: <1352467202-27903-2-git-send-email-thierry.reding@avionic-design.de>

On 09.11.2012 15:20, Thierry Reding wrote:
> This commit adds the host1x node along with its children to the Tegra20
> DTSI. Furthermore the OF auxiliary data table is updated to have proper
> names assigned to the platform devices instantiated from the device
> tree. Moreover, the clocks required by host1x and the two display
> controllers are initialized and the pll_d frequency table is completed
> with a few entries to support common HDMI and LVDS display modes.

I tried to add nvhost on top of your patches and I noticed a glitch.

> +       { "host1x",     "pll_c",        144000000,      false },

This line causes host1x not to operate correctly. I don't know why this
is so, but when I try to initialize host1x, it hangs with this change,
but everything works without this line.

If you could fix that,

Acked-by: Terje Bergstrom <tbergstrom@nvidia.com>

Best regards,
Terje


  parent reply	other threads:[~2012-11-14  8:32 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 host1x support 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 [this message]
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
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=50A357D3.9080002@nvidia.com \
    --to=tbergstrom@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@avionic-design.de \
    /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).