Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Tony Lindgren <tony@atomide.com>,
	"Mark A. Greer" <mgreer@animalcreek.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: Status of 1GHz support on am37xx
Date: Tue, 26 Nov 2013 09:49:27 -0600	[thread overview]
Message-ID: <5294C307.1080703@ti.com> (raw)
In-Reply-To: <20131125233545.GZ10023@atomide.com>

On 11/25/2013 05:35 PM, Tony Lindgren wrote:
> * Mark A. Greer <mgreer@animalcreek.com> [131122 15:02]:
>> Hello.
>>
>> I was wondering what that the status of 1GHz support for the am37xx is.
>>
>> It looks like smartreflex/avs and ABB drivers are there.  Do they need
>> more work (e.g., DT support)?  What DT nodes and related support need
>> to be added?
>>
>> What pieces are being worked on and which ones aren't?
>> Is there an ETA for the pieces being worked on?
> 
> There are still various parts of twl4030 that are only working with
> platform data, so at least those should be fixed now that we're moving
> to DT only based booting for mach-omap2 for v3.14.
> 

For 3630/DM3730 1GHz support the following needs to be done:
a) clock nodes[1] without which cpufreq-cpu0 will never scale frequencies
The following includes conversion to device tree enabled support.
b) VC-vp regulator
c) ABB dt nodes
d) AVS class 1.5 support
e) voltage regulator notifier around clock node for mpu so that avs
and abb can be sequenced around voltage and frequency changes.

So, to answer your question, we are a little farther away beyond the
first step of DT only boot to being able to exercise 1GHz properly.

[1] http://marc.info/?l=linux-omap&m=138545331825036&w=2
-- 
Regards,
Nishanth Menon

  reply	other threads:[~2013-11-26 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22 23:01 Status of 1GHz support on am37xx Mark A. Greer
2013-11-25 23:35 ` Tony Lindgren
2013-11-26 15:49   ` Nishanth Menon [this message]
2013-11-27 23:33     ` Mark A. Greer

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=5294C307.1080703@ti.com \
    --to=nm@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mgreer@animalcreek.com \
    --cc=tony@atomide.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