From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv5] omap3: Add basic support for 720MHz part
Date: Thu, 06 Feb 2014 20:26:56 +0100 [thread overview]
Message-ID: <1623915.4eAJkBo57q@avalon> (raw)
In-Reply-To: <1527616.Ycr1jOn0QT@avalon>
Hi all,
On Friday 22 June 2012 11:33:51 Laurent Pinchart wrote:
> On Thursday 10 February 2011 08:45:00 Kevin Hilman wrote:
> > Sanjeev Premi <premi@ti.com> writes:
> > > This patch adds support for speed enhanced variant of OMAP35x
> > > processors. These parts allow ARM and IVA running at 720MHz
> > > and 520MHz respectively.
> > >
> > > These parts can be detected at runtime by reading contents of
> > > PRODID.SKUID[3:0] at 0x4830A20C [1].
> > >
> > > This patch specifically does following:
> > > * Add new OPP to omap34xx_opp_def_list[] - disabled by default.
> > > * Detect devices capable of running at new OPP.
> > > * Enable new OPP only if device supports it.
> > > * Check for presence of IVA before attempting to enable the
> > >
> > > corresponding OPP.
> > >
> > > [1] http://focus.ti.com/lit/ug/spruff1d/spruff1d.pdf
> > >
> > > It appears from discussions (on this patch) that a variant of
> > > OMAP3430 supports this OPP but lacks runtime detection. This
> > >
> > > OPP can be enabled for these device by either:
> > > 1) Setting the bit corresponding to OMAP3_HAS_720MHZ
> > >
> > > in 'omap3_features'. (Refer changes to id.c)
> > >
> > > 2) Removing check for omap3_has_720mhz() before enabling
> > >
> > > the OPP. (Refer changes to opp3xxx_data.c)
> > >
> > > 3) Calling opp_enable() for 720MHz/VDD1 and 520MHz/VDD2 in
> > >
> > > the board file. (Refer changes to opp3xxx_data.c).
> > > This should, ideally, be done before omap3_opp_init() is
> > > called during device_initcall().
> > >
> > > CAUTION: This should be done for identified parts only.
> > >
> > > Else, the device could be damaged permanently.
> > >
> > > Signed-off-by: Sanjeev Premi <premi@ti.com>
> > > Reviewed-by: G, Manjunath Kondaiah <manjugk@ti.com>
> >
> > Acked-by: Kevin Hilman <khilman@ti.com>
>
> This patch seems to never have made it upstream. Is there a reason for that
> ?
Ping ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-02-06 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 8:10 [PATCHv5] omap3: Add basic support for 720MHz part Sanjeev Premi
2011-02-10 16:45 ` Kevin Hilman
2012-06-22 9:33 ` Laurent Pinchart
2014-02-06 19:26 ` Laurent Pinchart [this message]
2014-02-07 13:51 ` Nishanth Menon
2014-02-10 12:17 ` Laurent Pinchart
2014-02-10 14:46 ` Nishanth Menon
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=1623915.4eAJkBo57q@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.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).