From: Archit Taneja <archit@ti.com>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: "Valkeinen, Tomi" <tomi.valkeinen@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] OMAPDSS: DISPC: VIDEO3 pipeline support
Date: Tue, 20 Sep 2011 12:25:37 +0530 [thread overview]
Message-ID: <4E7838E9.6000802@ti.com> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E739404EC811422@dbde02.ent.ti.com>
Hi,
On Tuesday 20 September 2011 01:13 AM, Hiremath, Vaibhav wrote:
>
>> -----Original Message-----
>> From: Taneja, Archit
>> Sent: Friday, September 16, 2011 12:09 PM
>> To: Valkeinen, Tomi
>> Cc: Hiremath, Vaibhav; linux-omap@vger.kernel.org; Taneja, Archit
>> Subject: [PATCH v2 2/3] OMAPDSS: DISPC: VIDEO3 pipeline support
>>
>> Add support for VIDEO3 pipeline on OMAP4:
>> - Add VIDEO3 pipeline information in dss_features and omapdss.h
>> - Add VIDEO3 pipeline register coefficients in dispc.h
>> - Create a new overlay structure corresponding to VIDEO3.
>> - Make changes in dispc.c for VIDEO3
>>
>> Signed-off-by: Archit Taneja<archit@ti.com>
<snip>
>> diff --git a/drivers/video/omap2/dss/dss_features.h
>> b/drivers/video/omap2/dss/dss_features.h
>> index e81271a..6a6c05d 100644
>> --- a/drivers/video/omap2/dss/dss_features.h
>> +++ b/drivers/video/omap2/dss/dss_features.h
>> @@ -25,7 +25,7 @@
>> #endif
>>
>> #define MAX_DSS_MANAGERS 3
>> -#define MAX_DSS_OVERLAYS 3
>> +#define MAX_DSS_OVERLAYS 4
> [Hiremath, Vaibhav] Not related to this patch as such, but I think we should now get rid of these macros and use run-time mechanism.
This macro is used within DSS2 to declare the size of some arrays. So a
runtime mechanism isn't possible(unless we allocate the arrays
dynamically itself, but they are used for trivial purposes, and won't be
large in size, so I don't think that this is needed).
We anyway use the function omap_dss_get_num_overlays() wherever possible.
>
> Overall this patch looks ok to me, I will test it tomorrow and will update you.
Thanks,
Archit
>
> Thanks,
> Vaibhav
>
>> #define MAX_DSS_LCD_MANAGERS 2
>> #define MAX_NUM_DSI 2
>>
>> diff --git a/drivers/video/omap2/dss/overlay.c
>> b/drivers/video/omap2/dss/overlay.c
>> index afb7583..11d21e3 100644
>> --- a/drivers/video/omap2/dss/overlay.c
>> +++ b/drivers/video/omap2/dss/overlay.c
>> @@ -615,6 +615,11 @@ void dss_init_overlays(struct platform_device *pdev)
>> ovl->id = OMAP_DSS_VIDEO2;
>> ovl->info.global_alpha = 255;
>> break;
>> + case 3:
>> + ovl->name = "vid3";
>> + ovl->id = OMAP_DSS_VIDEO3;
>> + ovl->info.global_alpha = 255;
>> + break;
>> }
>>
>> ovl->set_manager =&omap_dss_set_manager;
>> diff --git a/include/video/omapdss.h b/include/video/omapdss.h
>> index 5f0ce5e..1f12559 100644
>> --- a/include/video/omapdss.h
>> +++ b/include/video/omapdss.h
>> @@ -41,6 +41,8 @@
>> #define DISPC_IRQ_WAKEUP (1<< 16)
>> #define DISPC_IRQ_SYNC_LOST2 (1<< 17)
>> #define DISPC_IRQ_VSYNC2 (1<< 18)
>> +#define DISPC_IRQ_VID3_END_WIN (1<< 19)
>> +#define DISPC_IRQ_VID3_FIFO_UNDERFLOW (1<< 20)
>> #define DISPC_IRQ_ACBIAS_COUNT_STAT2 (1<< 21)
>> #define DISPC_IRQ_FRAMEDONE2 (1<< 22)
>> #define DISPC_IRQ_FRAMEDONEWB (1<< 23)
>> @@ -63,7 +65,8 @@ enum omap_display_type {
>> enum omap_plane {
>> OMAP_DSS_GFX = 0,
>> OMAP_DSS_VIDEO1 = 1,
>> - OMAP_DSS_VIDEO2 = 2
>> + OMAP_DSS_VIDEO2 = 2,
>> + OMAP_DSS_VIDEO3 = 3,
>> };
>>
>> enum omap_channel {
>> --
>> 1.7.1
>
>
next prev parent reply other threads:[~2011-09-20 6:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 6:39 [PATCH v2 0/3] OMAPDSS: DISPC: VIDEO3 and ZORDER support Archit Taneja
2011-09-16 6:39 ` [PATCH v2 1/3] OMAPDSS/OMAP_VOUT: Fix incorrect OMAP3-alpha compatibility setting Archit Taneja
2011-09-16 6:39 ` Archit Taneja
2011-09-19 19:36 ` Hiremath, Vaibhav
2011-09-20 6:44 ` Archit Taneja
2011-09-16 6:39 ` [PATCH v2 2/3] OMAPDSS: DISPC: VIDEO3 pipeline support Archit Taneja
2011-09-19 19:43 ` Hiremath, Vaibhav
2011-09-20 6:55 ` Archit Taneja [this message]
2011-09-16 6:39 ` [PATCH v2 3/3] OMAPDSS: DISPC: zorder support for DSS overlays Archit Taneja
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=4E7838E9.6000802@ti.com \
--to=archit@ti.com \
--cc=hvaibhav@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.