Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Raghu <raghavendra.kh@gmail.com>
Cc: Kevin Hilman <khilman@ti.com>, Paul Walmsley <paul@pwsan.com>,
	linux-omap mailing list <linux-omap@vger.kernel.org>
Subject: Re: OMAP PM constraint to disable OPP50
Date: Mon, 27 Feb 2012 19:41:11 +0200	[thread overview]
Message-ID: <1330364471.2205.261.camel@deskari> (raw)
In-Reply-To: <CAHu_vbqvXja0tGYyj4OgwvQEhfpgLq7BiK+f3mAGEExzbATksQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 812 bytes --]

On Mon, 2012-02-27 at 11:32 -0600, Raghu wrote:
> On Thu, Feb 23, 2012 at 1:28 AM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
> >
> > Hi,
> >
> > This is an old issue, and I've mentioned earlier, but I think we should
> > finally do something about this. Or perhaps this can already be done,
> > but I don't know the solution.
> 
> I agree with you.
> We need to address the L3 bandwidth requirement for DSS as needed by
> high resolution panels.

That is a different problem. There are to PM constraints from DSS:

- L3 bandwidth, depending on the pixel clock, resolution, color format,
etc.
- Maximum DSS clock frequencies

The first one is not trivial, but it should be possible to implement it
inside omapdss driver. The second one is the problem case my email was
about.

 Tomi


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-02-27 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23  7:28 OMAP PM constraint to disable OPP50 Tomi Valkeinen
2012-02-27 17:32 ` Raghu
2012-02-27 17:41   ` Tomi Valkeinen [this message]

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=1330364471.2205.261.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=raghavendra.kh@gmail.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