linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Prashant Gaikwad <pgaikwad@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
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 v2 0/6] Port Tegra to generic clk framework
Date: Wed, 4 Jul 2012 11:08:05 +0530	[thread overview]
Message-ID: <4FF3D6BD.1000509@nvidia.com> (raw)
In-Reply-To: <4FF31DFC.8030708@wwwdotorg.org>

On Tuesday 03 July 2012 09:59 PM, Stephen Warren wrote:
> On 07/03/2012 05:09 AM, Prashant Gaikwad wrote:
>> This patch set ports Tegra clock code to generic clock framework.
>>
>> Depends on
>> [PATCH v3 0/9] Add clk_prepare/clk_unprepare series
>> [PATCH] ARM: tegra: Remove second instance of uart clk
>> [PATCH] dma: tegra: add clk_prepare/clk_unprepare
>> [PATCH] ARM: tegra: dma: rename driver name for clock to "tegra-apbdma"
>>
>> Tested on Ventana and Cardhu
>>
>> v2:
>>   - Rebased on Tegra's for-3.6/common-clk
> OK, this applies to for-3.6/common-clk without issue now. However, there
> are still runtime problems:
>
> On Tegra20(Ventana), running Tegra's for-next branch with these patches
> merged in, if I play audio, the sound is much too low a pitch; the I2S
> clock must be being set too low. Also, if I play the same file twice,
> once encoded as 48KHz once encoded as 44.1KHz, the pitch is different.
>
> On Tegra20(Ventana), running next-20120703 plus a few local patches for
> regulators plus these common clock patches, then I see the same
> segfaults during boot that I mentioned before. It seems something in
> linux-next not in Tegra's for-next branch is breaking the common clock
> code for us.

Does these local patches include any changes in clock init table? Is it 
possible to share the changes?

> Neither problem is seen on Cardhu with the same kernels.
>
> Can you please investigate and fix these issues? Thanks.


  reply	other threads:[~2012-07-04  5:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03 11:09 [PATCH v2 0/6] Port Tegra to generic clk framework Prashant Gaikwad
2012-07-03 11:09 ` [PATCH v2 1/6] ARM: tegra30: Separate out clk ops and clk data Prashant Gaikwad
2012-07-03 11:09 ` [PATCH v2 2/6] ARM: tegra20: " Prashant Gaikwad
2012-07-03 11:09 ` [PATCH v2 3/6] ARM: tegra: Rename tegra20 clock file Prashant Gaikwad
2012-07-03 11:09 ` [PATCH v2 4/6] ARM: tegra: Add clk_tegra structure and helper functions Prashant Gaikwad
2012-07-03 11:09 ` [PATCH v2 5/6] ARM: tegra: Port tegra to generic clock framework Prashant Gaikwad
2012-07-03 11:09 ` [PATCH v2 6/6] ARM: tegra: Remove duplicate code Prashant Gaikwad
2012-07-03 16:29 ` [PATCH v2 0/6] Port Tegra to generic clk framework Stephen Warren
2012-07-04  5:38   ` Prashant Gaikwad [this message]
2012-07-05 15:32     ` Stephen Warren
2012-07-05 16:02       ` Prashant Gaikwad

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=4FF3D6BD.1000509@nvidia.com \
    --to=pgaikwad@nvidia.com \
    --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=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).