All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Archit Taneja <archit@ti.com>
Cc: linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/2] OMAPDSS: DISPC: Update manager size limits for OMAP5
Date: Tue, 20 Nov 2012 14:54:47 +0000	[thread overview]
Message-ID: <50AB99B7.9030102@ti.com> (raw)
In-Reply-To: <1352881216-7490-1-git-send-email-archit@ti.com>

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

On 2012-11-14 10:20, Archit Taneja wrote:
> Manager width and height can go up to 4K on OMAP5. Make manager width and height
> register field offsets and maximum limits as dispc_features. Create a new
> dispc_feature struct for OMAP5 which highlights this difference.
> 
> Archit Taneja (2):
>   OMAPDSS: Add overlay manager width and height limits as a dispc
>     feature
>   OMAPDSS: Add a dispc_features struct for OMAP5
> 
>  drivers/video/omap2/dss/dispc.c        |   47 +++++++++++++++++++++++++++++---
>  drivers/video/omap2/dss/dss_features.c |    8 ------
>  drivers/video/omap2/dss/dss_features.h |    2 --
>  3 files changed, 43 insertions(+), 14 deletions(-)
> 

Thanks, looks fine. I'll apply to omapdss tree.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 897 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Archit Taneja <archit@ti.com>
Cc: linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/2] OMAPDSS: DISPC: Update manager size limits for OMAP5
Date: Tue, 20 Nov 2012 16:54:47 +0200	[thread overview]
Message-ID: <50AB99B7.9030102@ti.com> (raw)
In-Reply-To: <1352881216-7490-1-git-send-email-archit@ti.com>

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

On 2012-11-14 10:20, Archit Taneja wrote:
> Manager width and height can go up to 4K on OMAP5. Make manager width and height
> register field offsets and maximum limits as dispc_features. Create a new
> dispc_feature struct for OMAP5 which highlights this difference.
> 
> Archit Taneja (2):
>   OMAPDSS: Add overlay manager width and height limits as a dispc
>     feature
>   OMAPDSS: Add a dispc_features struct for OMAP5
> 
>  drivers/video/omap2/dss/dispc.c        |   47 +++++++++++++++++++++++++++++---
>  drivers/video/omap2/dss/dss_features.c |    8 ------
>  drivers/video/omap2/dss/dss_features.h |    2 --
>  3 files changed, 43 insertions(+), 14 deletions(-)
> 

Thanks, looks fine. I'll apply to omapdss tree.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 897 bytes --]

  parent reply	other threads:[~2012-11-20 14:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14  8:20 [PATCH 0/2] OMAPDSS: DISPC: Update manager size limits for OMAP5 Archit Taneja
2012-11-14  8:32 ` Archit Taneja
2012-11-14  8:20 ` [PATCH 1/2] OMAPDSS: Add overlay manager width and height limits as a dispc feature Archit Taneja
2012-11-14  8:32   ` Archit Taneja
2012-11-14  8:20 ` [PATCH 2/2] OMAPDSS: Add a dispc_features struct for OMAP5 Archit Taneja
2012-11-14  8:32   ` Archit Taneja
2012-11-20 14:54 ` Tomi Valkeinen [this message]
2012-11-20 14:54   ` [PATCH 0/2] OMAPDSS: DISPC: Update manager size limits " Tomi Valkeinen

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=50AB99B7.9030102@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=archit@ti.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    /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.