public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Prashant Gaikwad <pgaikwad@nvidia.com>
Cc: "mturquette@ti.com" <mturquette@ti.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
	"ccross@android.com" <ccross@android.com>,
	"olof@lixom.net" <olof@lixom.net>,
	Peter De Schrijver <pdeschrijver@nvidia.com>
Subject: Re: [PATCH v3 0/6] Port Tegra to generic clk framework
Date: Fri, 06 Jul 2012 10:15:18 -0600	[thread overview]
Message-ID: <4FF70F16.50205@wwwdotorg.org> (raw)
In-Reply-To: <4FF6F7CF.9000405@nvidia.com>

On 07/06/2012 08:35 AM, Prashant Gaikwad wrote:
> On Friday 06 July 2012 12:19 AM, Stephen Warren wrote:
>> On 07/05/2012 03:55 AM, Prashant Gaikwad wrote:
>>> This patch set ports Tegra clock code to generic clock framework.
> <snip>
>> (The one slight difference between the 2 branches I tested is that AC100
>> and Trimslice booted using DT passed in next-20120705 but failed only in
>> Tegra's for-next. Otherwise, all results were identical)
>>
>> I'll try to investigate what the issues are since I imagine you don't
>> have access to these boards. But, I probably won't be able to fix this
>> until I return from vacation.
> 
> Stephen,
> 
> Can you please try removing "late_initcall(clk_disable_unused);" from
> drivers/clk/clk.c?
> It will keep unused clocks enabled. If it works then there should not be
> any regression in this patch series but need to enable some board
> specific clock.

On Whistler using next-20120705, that did help a bit; the board actually
boots to the login prompt in the usual amount of time rather than
hanging before even detecting the root filesystem.

However, there is obviously still some problem with I2C accesses, since
neither the pca953x nor wm8753 drivers are able to communicate with
their devices.

Re: the DT-vs-non-DT differences, it's most likely because only parts of
the clock initialization table are common (in common.c) and parts are in
board-${boardname}.c (for non-DT) or board-dt-tegra*.c (for DT). I'm
looking forward to when we can just put all the clock setup in the
board-specific .dts files:-)

I'll investigate more later (where most later might mostly be in 2 weeks
after I return from vacation)

      reply	other threads:[~2012-07-06 16:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-05  9:55 [PATCH v3 0/6] Port Tegra to generic clk framework Prashant Gaikwad
2012-07-05  9:55 ` [PATCH v3 1/6] ARM: tegra30: Separate out clk ops and clk data Prashant Gaikwad
2012-07-05  9:55 ` [PATCH v3 2/6] ARM: tegra20: " Prashant Gaikwad
2012-07-05  9:55 ` [PATCH v3 3/6] ARM: tegra: Rename tegra20 clock file Prashant Gaikwad
2012-07-05  9:55 ` [PATCH v3 4/6] ARM: tegra: Add clk_tegra structure and helper functions Prashant Gaikwad
2012-07-05  9:55 ` [PATCH v3 5/6] ARM: tegra: Port tegra to generic clock framework Prashant Gaikwad
2012-07-05  9:55 ` [PATCH v3 6/6] ARM: tegra: Remove duplicate code Prashant Gaikwad
2012-07-05 18:49 ` [PATCH v3 0/6] Port Tegra to generic clk framework Stephen Warren
2012-07-06  3:57   ` Prashant Gaikwad
2012-07-06 14:35   ` Prashant Gaikwad
2012-07-06 16:15     ` Stephen Warren [this message]

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=4FF70F16.50205@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=ccross@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mturquette@ti.com \
    --cc=olof@lixom.net \
    --cc=pdeschrijver@nvidia.com \
    --cc=pgaikwad@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