From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] include: fb: Add definiton for window positioning
Date: Tue, 20 Sep 2011 11:10:21 +0000	[thread overview]
Message-ID: <1316517021.1949.13.camel@deskari> (raw)
In-Reply-To: <1316532641-2657-2-git-send-email-ajaykumar.rs@samsung.com>
On Tue, 2011-09-20 at 11:30 -0400, Ajay Kumar wrote:
> This patch adds a data structure definiton to hold framebuffer windows/planes.
> An ioctl number is also added to provide user access
> to change window position dynamically.
> 
> Signed-off-by: Ajay Kumar <ajaykumar.rs@samsung.com>
> Signed-off-by: Banajit Goswami <banajit.g@samsung.com>
> Suggested-by: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
>  include/linux/fb.h |    7 +++++++
>  1 files changed, 7 insertions(+), 0 deletions(-)
> 
> diff --git a/include/linux/fb.h b/include/linux/fb.h
> index 1d6836c..2141941 100644
> --- a/include/linux/fb.h
> +++ b/include/linux/fb.h
> @@ -39,6 +39,7 @@
>  #define FBIOPUT_MODEINFO        0x4617
>  #define FBIOGET_DISPINFO        0x4618
>  #define FBIO_WAITFORVSYNC	_IOW('F', 0x20, __u32)
> +#define FBIOPOS_OVERLAY_WIN	_IOW('F', 0x21, struct fb_overlay_win_pos)
>  
>  #define FB_TYPE_PACKED_PIXELS		0	/* Packed Pixels	*/
>  #define FB_TYPE_PLANES			1	/* Non interleaved planes */
> @@ -366,6 +367,12 @@ struct fb_image {
>  	struct fb_cmap cmap;	/* color map info */
>  };
>  
> +/* Window overlaying */
> +struct fb_overlay_win_pos {
> +	__u32 win_pos_x;	/* x-offset from LCD(0,0) where window starts */
> +	__u32 win_pos_y;	/* y-offset from LCD(0,0) where window starts */
> +};
Shouldn't this also include the window size (in case scaling is
supported)?
This also won't work for setups where the same framebuffer is used by
multiple overlays. For example, this is the case on OMAP when the same
content is cloned to, say, LCD and TV, each of which is showing an
overlay.
 Tomi
next prev parent reply	other threads:[~2011-09-20 11:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20  9:28 [PATCH 0/3] FB: Add window positioning support Ajay Kumar
2011-09-20  9:29 ` [PATCH 3/3] video: s3c-fb: Modify s3c-fb driver to support window Ajay Kumar
2011-09-20  9:29 ` [PATCH 1/3] include: fb: Add definiton for window positioning structure Ajay Kumar
2011-09-20 11:10   ` Tomi Valkeinen [this message]
2011-09-20 14:58     ` Ajay kumar
2011-09-20 15:39       ` [PATCH 1/3] include: fb: Add definiton for window positioning Tomi Valkeinen
2011-09-20 16:55         ` Florian Tobias Schandinat
2011-09-20 18:57           ` Tomi Valkeinen
2011-09-21  7:27           ` [PATCH 1/3] include: fb: Add definiton for window positioning structure Ajay kumar
2011-09-20 11:24   ` [PATCH 1/3] include: fb: Add definiton for window positioning Baruch Siach
2011-09-20 15:38     ` [PATCH 1/3] include: fb: Add definiton for window positioning structure Ajay kumar
2011-09-20 17:08       ` [PATCH 1/3] include: fb: Add definiton for window positioning Baruch Siach
2011-09-21  6:25         ` Tomi Valkeinen
2011-09-21  7:30           ` [PATCH 1/3] include: fb: Add definiton for window positioning structure Ajay kumar
2011-09-20  9:29 ` [PATCH 2/3] ARM: SAMSUNG: Embed window positioning data structure in Ajay Kumar
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=1316517021.1949.13.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).