From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: "ext Taneja, Archit" <archit@ti.com>
Cc: "Semwal, Sumit" <sumit.semwal@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: RE: DSS2 patch series
Date: Thu, 05 Aug 2010 11:09:42 +0300 [thread overview]
Message-ID: <1280995782.3436.205.camel@tubuntu.research.nokia.com> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC3560870306287736@dbde02.ent.ti.com>
On Thu, 2010-08-05 at 09:06 +0200, ext Taneja, Archit wrote:
> Hi,
>
> >
> > Also, we should think how to reduce if (cpu_is_omap44xx())
> > lines. There should be some kind of DSS capability list
> > somewhere, which would tell the features available. I haven't
> > thought this more, but it'd be very nice if we could use the
> > DSS HW version number to decide what features there are.
> >
> > However, TI answered that information about DSS HW version
> > numbers is not available, and thus cannot be used =(. Perhaps
> > you could try to dig out some information from inside TI?
> >
>
> I read the DSS_REVISON, DISPC_REVISION etc registers on 3430, 3630, 4430:
>
> 3430: DSS rev 2.0, DISPC rev 3.0, RFBI rev 1.0, DSI rev 1.0, VENC rev 2
> 3630: DSS rev 2.0, DISPC rev 3.0, RFBI rev 1.0, DSI rev 1.0, VENC rev 2
> 4430: DSS rev 4.0, DISPC rev 4.0, DSI rev 3.0, RFBI rev 3.5
>
> I haven't tried on OMAP2 yet..
>
> Don't you think these revision numbers are enough to differentiate the
> features of each IP block?
Perhaps. The problem is, I don't know what the version numbers mean, ie.
when are they changed, what are the changes. I would hope you that you
could find some internal info inside TI that would explain the
differences =).
We can of course reverse engineer the version numbers, and hope that we
decipher them correctly. For OMAP3430/3630/4430 the differences look
clear.
But how about OMAP rev changes? For example, at some 3430 revision the
bitfield lengths of video timing registers were changed. Does it show on
DSS/DISPC version numbers? I don't think I have boards with those revs,
so I can't check.
Tomi
next prev parent reply other threads:[~2010-08-05 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 8:27 DSS2 patch series Taneja, Archit
2010-08-02 11:51 ` Tomi Valkeinen
2010-08-02 12:05 ` Taneja, Archit
2010-08-03 8:43 ` Tomi Valkeinen
2010-08-03 9:00 ` Taneja, Archit
2010-08-05 7:06 ` Taneja, Archit
2010-08-05 8:09 ` Tomi Valkeinen [this message]
2010-08-10 9:33 ` Taneja, Archit
2010-08-17 10:52 ` Tomi Valkeinen
2010-08-17 11:16 ` Taneja, Archit
2010-08-17 11:32 ` Cousson, Benoit
2010-08-19 18:43 ` Taneja, Archit
2010-08-17 11:39 ` Tomi Valkeinen
2010-08-19 21:33 ` Taneja, Archit
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=1280995782.3436.205.camel@tubuntu.research.nokia.com \
--to=tomi.valkeinen@nokia.com \
--cc=archit@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=sumit.semwal@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