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 v3 0/6] Port Tegra to generic clk framework
Date: Fri, 6 Jul 2012 09:27:06 +0530 [thread overview]
Message-ID: <4FF66212.6080507@nvidia.com> (raw)
In-Reply-To: <4FF5E1C3.6070309@wwwdotorg.org>
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.
> Unfortunately, this series causes some regressions, so I can't apply it
> now. Given that, it won't make 3.6 since I won't be around to apply it.
Ok.
> I tested both Tegra's for-next, and next-20120705, both plus this
> series, next-20120705 plus the fix for the common clock code
> __clk_set_parent() issue.
>
> The following all appeared to work OK:
>
> Cardhu DT
> Ventana DT
> Seaboard DT
> Springbank DT
> Harmony DT
> Harmony non-DT
>
> However, the following failed, all(?) in ways that prevented the system
> getting to the login prompt:
>
> Whistler DT
> AC100 DT
> AC100 non-DT
> Trimslice DT
> Trimslice non-DT
>
> (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.
I am not sure how DT/non-DT should make difference to this series.
I don't have access to those boards but if you can share the failure log
I can try to pinpoint the fix.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: pgaikwad@nvidia.com (Prashant Gaikwad)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/6] Port Tegra to generic clk framework
Date: Fri, 6 Jul 2012 09:27:06 +0530 [thread overview]
Message-ID: <4FF66212.6080507@nvidia.com> (raw)
In-Reply-To: <4FF5E1C3.6070309@wwwdotorg.org>
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.
> Unfortunately, this series causes some regressions, so I can't apply it
> now. Given that, it won't make 3.6 since I won't be around to apply it.
Ok.
> I tested both Tegra's for-next, and next-20120705, both plus this
> series, next-20120705 plus the fix for the common clock code
> __clk_set_parent() issue.
>
> The following all appeared to work OK:
>
> Cardhu DT
> Ventana DT
> Seaboard DT
> Springbank DT
> Harmony DT
> Harmony non-DT
>
> However, the following failed, all(?) in ways that prevented the system
> getting to the login prompt:
>
> Whistler DT
> AC100 DT
> AC100 non-DT
> Trimslice DT
> Trimslice non-DT
>
> (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.
I am not sure how DT/non-DT should make difference to this series.
I don't have access to those boards but if you can share the failure log
I can try to pinpoint the fix.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-07-06 3:57 UTC|newest]
Thread overview: 32+ 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 ` Prashant Gaikwad
2012-07-05 9:55 ` Prashant Gaikwad
2012-07-05 9:55 ` [PATCH v3 2/6] ARM: tegra20: Separate out clk ops and clk data Prashant Gaikwad
2012-07-05 9:55 ` Prashant Gaikwad
2012-07-05 9:55 ` 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 ` Prashant Gaikwad
2012-07-05 9:55 ` 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 ` Prashant Gaikwad
2012-07-05 9:55 ` Prashant Gaikwad
[not found] ` <1341482120-3317-1-git-send-email-pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
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 ` Prashant Gaikwad
2012-07-05 9:55 ` Prashant Gaikwad
2012-07-05 9:55 ` [PATCH v3 3/6] ARM: tegra: Rename tegra20 clock file Prashant Gaikwad
2012-07-05 9:55 ` Prashant Gaikwad
2012-07-05 9:55 ` Prashant Gaikwad
2012-07-05 9:55 ` [PATCH v3 6/6] ARM: tegra: Remove duplicate code Prashant Gaikwad
2012-07-05 9:55 ` Prashant Gaikwad
2012-07-05 9:55 ` Prashant Gaikwad
2012-07-05 18:49 ` [PATCH v3 0/6] Port Tegra to generic clk framework Stephen Warren
2012-07-05 18:49 ` Stephen Warren
2012-07-05 18:49 ` Stephen Warren
2012-07-06 3:57 ` Prashant Gaikwad [this message]
2012-07-06 3:57 ` Prashant Gaikwad
[not found] ` <4FF5E1C3.6070309-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-07-06 14:35 ` Prashant Gaikwad
2012-07-06 14:35 ` Prashant Gaikwad
2012-07-06 14:35 ` Prashant Gaikwad
[not found] ` <4FF6F7CF.9000405-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-07-06 16:15 ` Stephen Warren
2012-07-06 16:15 ` Stephen Warren
2012-07-06 16:15 ` Stephen Warren
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=4FF66212.6080507@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.