public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Peter Barada <peter.barada@logicpd.com>,
	Ashwin Bihari <abihari@gmail.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Linux 3.0 DSS support
Date: Thu, 03 Nov 2011 11:46:18 +0200	[thread overview]
Message-ID: <1320313578.1859.55.camel@deskari> (raw)
In-Reply-To: <49A85CFF-CB0B-435C-BB54-12D247ABB6BE@dominion.thruhere.net>

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

On Thu, 2011-11-03 at 10:35 +0100, Koen Kooi wrote:
> Op 25 okt. 2011, om 09:37 heeft Tomi Valkeinen het volgende geschreven:
> 
> > Hi,
> > 
> > On Mon, 2011-10-24 at 13:55 -0400, Peter Barada wrote:
> >> 
> >> In the above case (and my case where I'm looking for a 9Mhz pixel 
> >> clock), fck_div is calculated at higher than 16 - and the video
> >> output 
> >> is wrong (i.e. no pixel clock and hsync runs at 32x the requested
> >> rate). 
> > 
> > DM37x TRM says:
> > 
> > "DSS1_ALWON_FCLK: Issued from DPLL4. Its frequency can be a division by
> > 1 to 16 of the frequency of the DPLL4 synthesized clock."
> > 
> > I take it that DM37x is detected as cpu_is_3630()?
> > 
> > The DSS driver currently handles only OMAPs, so for other SoCs the
> > driver may contain lots of bugs like this.
> 
> dm3730 is just a different marketing name for omap3630, it should not have any functional changes.

According to the TRM and experiments by Peter, it does.

 Tomi


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

  reply	other threads:[~2011-11-03  9:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANLagX8WaHGkqOZ2UnLR1ihOABbdDy1ZAyW19yO=f-JNUaLKfw@mail.gmail.com>
2011-10-17  7:19 ` Linux 3.0 DSS support Tomi Valkeinen
     [not found]   ` <CANLagX9R9DKi1MCa11t4REDFzRgXdJQWxNG4Q6mv46f8dACdSQ@mail.gmail.com>
2011-10-19 13:27     ` Ashwin Bihari
2011-10-24 17:55   ` Peter Barada
2011-10-25  7:37     ` Tomi Valkeinen
2011-11-02 15:42       ` Peter Barada
2011-11-03  9:35       ` Koen Kooi
2011-11-03  9:46         ` Tomi Valkeinen [this message]
2011-11-03 14:50           ` Peter Barada

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=1320313578.1859.55.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=abihari@gmail.com \
    --cc=koen@dominion.thruhere.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.barada@logicpd.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