mirror of https://lore.kernel.org/lkml/
 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 12:23:42 +0200	[thread overview]
Message-ID: <50A3712E.7000104@nvidia.com> (raw)
In-Reply-To: <20121114084931.GA31837@avionic-0098.mockup.avionic-design.de>

On 14.11.2012 10:49, Thierry Reding wrote:
> Can you find out how the host1x clock is setup without this change? I
> was told that freezes can occur when you try to access the registers
> without the host1x clock being enabled. However, the host1x driver
> should take care to properly setup the clock.
> 
> To find out if the non-running clock is the issue, can you try to patch
> that line and make the final element true instead of false? That should
> enable the clock on boot so that it should always be running.

I tried with fastboot and U-Boot, and whenever that line is there,
kernel boot will halt at nvhost init. Same happens if I just change the
false to true.

nvhost will enable the clock and disable as it need. Also, part of
host1x initialization did proceed, but it ended up hanging after a few
registers were initialized. So it's not a case of host1x being off, but
host1x hanging after a while.

If I change this line to:

       { "host1x",     "pll_p",        216000000,      false },

it will also work properly. It looks like we have some problem with
pll_c in Tegra20, or clock configuration with your patch. In Tegra30,
pll_c with 144MHz seems to work fine, but on Tegra20, it doesn't.

In internal kernel, we use pll_c for host1x, so hardware shouldn't be
the problem here.

Best regards,
Terje

  reply	other threads:[~2012-11-14 10:20 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 [this message]
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=50A3712E.7000104@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

Powered by JetHome