From: Kevin Hilman <khilman@ti.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com, b-cousson@ti.com
Subject: Re: [PATCH 0/7] OMAP4: Add 4460 base support
Date: Fri, 01 Jul 2011 09:40:07 -0700 [thread overview]
Message-ID: <1309538407.6231.84.camel@vence> (raw)
In-Reply-To: <87boxe2c1q.fsf@ti.com>
On Fri, 2011-07-01 at 09:36 -0700, Kevin Hilman wrote:
> Rajendra Nayak <rnayak@ti.com> writes:
>
> > This series adds base support needed to be able
> > to boot on a OMAP4460 device.
> > Patches are based on Benoit's for_3.0.1/7_hwmod_modulemode
> > branch and boot tested on both 4460sdp as well as 4430sdp.
>
> Can you also briefly summarize the dependencies between this series an
> Benoit's? I'm assuming it is mainly because of the s/4430/44XX/
> changes, and also avoiding conflicts in clockdomain and powerdomain data
> files.
>
> With that, you can add
>
> Reviewed-by: Kevin Hilman <khilman@ti.com>
>
> for the whole series.
oops, except for [7/7], where I agree with Tony.
As discussed off-list, lets just drop this patch all together and state
in [0/7] that there is a limitation that until we fix the hwmod fwk to
do lazy disable as Tony suggested, 4460 can only reliably boot at OPP50.
Kevin
next prev parent reply other threads:[~2011-07-01 16:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 2:07 [PATCH 0/7] OMAP4: Add 4460 base support Rajendra Nayak
2011-07-01 2:07 ` [PATCH 1/7] OMAP: ID: introduce chip detection for OMAP4460 Rajendra Nayak
2011-07-01 2:07 ` [PATCH 2/7] OMAP4: ID: add omap_has_feature for max freq supported Rajendra Nayak
2011-07-01 2:07 ` [PATCH 3/7] OMAP4: PRCM: OMAP4460 specific PRM and CM register bitshifts Rajendra Nayak
2011-07-01 2:07 ` [PATCH 4/7] OMAP4: clocks: Update the clock tree with 4460 clock nodes Rajendra Nayak
2011-07-01 2:07 ` [PATCH 5/7] OMAP4: powerdomain: Reuse on 4460 using CHIP_IS_44XX Rajendra Nayak
2011-07-01 2:08 ` [PATCH 6/7] OMAP4: clockdomain: " Rajendra Nayak
2011-07-01 2:08 ` [PATCH 7/7] 4460sdp/blaze/panda: hwmod: Prevent gpio1 reset during hwmod init Rajendra Nayak
2011-07-01 6:32 ` Tony Lindgren
2011-07-03 4:14 ` Paul Walmsley
2011-07-04 8:53 ` Tony Lindgren
2011-07-05 7:40 ` Paul Walmsley
2011-07-05 10:45 ` Tony Lindgren
2011-07-05 21:47 ` Paul Walmsley
2011-07-06 6:47 ` Tony Lindgren
2011-07-01 2:41 ` [PATCH 2/7] OMAP4: ID: add omap_has_feature for max freq supported Todd Poynor
2011-07-01 4:48 ` Aneesh V
2011-07-01 6:25 ` [PATCH 1/7] OMAP: ID: introduce chip detection for OMAP4460 Tony Lindgren
2011-07-01 10:15 ` Aneesh V
2011-07-01 16:31 ` [PATCH 0/7] OMAP4: Add 4460 base support Kevin Hilman
2011-07-01 16:36 ` Kevin Hilman
2011-07-01 16:40 ` Kevin Hilman [this message]
2011-07-01 17:00 ` Rajendra Nayak
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=1309538407.6231.84.camel@vence \
--to=khilman@ti.com \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.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