From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Archit Taneja <archit@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Sumit Semwal <sumit.semwal@ti.com>,
Mukund Mittal <mmittal@ti.com>, Samreen <samreen@ti.com>
Subject: Re: [PATCH v4 3/7] OMAP: DSS2: Introduce omap_channel as a omap_dss_device parameter
Date: Tue, 16 Nov 2010 12:55:57 +0200 [thread overview]
Message-ID: <1289904957.2668.75.camel@tubuntu> (raw)
In-Reply-To: <1289219065-1362-4-git-send-email-archit@ti.com>
Hi,
On Mon, 2010-11-08 at 13:24 +0100, ext Archit Taneja wrote:
> From: Sumit Semwal <sumit.semwal@ti.com>
>
> A new member 'channel' is introduced in omap_dss_device structure to determine
> which channel the panel uses. The dispc functions used by interface drivers
> (dsi, sdi etc) will use this member to differentiate between the 2 channels.
>
> The following dispc functions are changed to incorporate channel as an argument:
> -dispc_enable_fifohandcheck()
> -dispc_set_lcd_size()
> -dispc_set_parallel_interface_mode()
> -dispc_set_tft_data_lines()
> -dispc_set_lcd_display_type()
> -dispc_set_lcd_timings()
>
> The calls to these functions from the interface drivers have been changed to
> incorporate the new channel argument.
>
> Signed-off-by: Sumit Semwal <sumit.semwal@ti.com>
> Signed-off-by: Mukund Mittal <mmittal@ti.com>
> Signed-off-by: Samreen <samreen@ti.com>
> ---
> arch/arm/plat-omap/include/plat/display.h | 1 +
> drivers/video/omap2/dss/dispc.c | 49 ++++++++++++++++-------------
> drivers/video/omap2/dss/dpi.c | 11 +++---
> drivers/video/omap2/dss/dsi.c | 13 ++++---
> drivers/video/omap2/dss/dss.h | 19 ++++++-----
> drivers/video/omap2/dss/rfbi.c | 19 ++++++-----
> drivers/video/omap2/dss/sdi.c | 14 +++++---
> 7 files changed, 70 insertions(+), 56 deletions(-)
>
> diff --git a/arch/arm/plat-omap/include/plat/display.h b/arch/arm/plat-omap/include/plat/display.h
> index 586944d..3e6eec1 100644
> --- a/arch/arm/plat-omap/include/plat/display.h
> +++ b/arch/arm/plat-omap/include/plat/display.h
> @@ -434,6 +434,7 @@ struct omap_dss_device {
> struct omap_overlay_manager *manager;
>
> enum omap_dss_display_state state;
> + enum omap_channel channel;
Isn't this the same as dssdev->manager->id?
Yes, this channel stuff is a bit confusing, even the enum "omap_channel"
is badly named (should at least have "dss" in it). But
omap_overlay_manager should represent the output pipe, so I don't think
there's need for channel field in dss_device.
I think in many places we could even pass omap_overlay_manager pointer
around, instead of omap_channel. However, for low level dispc functions
it's perhaps cleaner to pass the channel ID though.
Tomi
next prev parent reply other threads:[~2010-11-16 10:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 12:24 [PATCH v4 0/7] OMAP: DSS2: Overlay Manager LCD2 support in DISPC Archit Taneja
2010-11-08 12:24 ` [PATCH v4 1/7] OMAP: DSS2: Add dss_features for omap4 and overlay manager related features Archit Taneja
2010-11-08 12:24 ` [PATCH v4 2/7] OMAP: DSS2: Represent DISPC register defines with channel as parameter Archit Taneja
2010-11-15 15:17 ` Tomi Valkeinen
2010-11-16 4:25 ` Taneja, Archit
2010-11-08 12:24 ` [PATCH v4 3/7] OMAP: DSS2: Introduce omap_channel as a omap_dss_device parameter Archit Taneja
2010-11-16 10:55 ` Tomi Valkeinen [this message]
2010-11-16 11:22 ` Taneja, Archit
2010-11-16 13:32 ` Tomi Valkeinen
2010-11-17 8:31 ` Taneja, Archit
2010-11-17 12:56 ` Taneja, Archit
2010-11-08 12:24 ` [PATCH v4 4/7] OMAP: DSS2: Change remaining Dispc functions for new 'channel' argument Archit Taneja
2010-11-08 12:24 ` [PATCH v4 5/7] OMAP: DSS2: LCD2 Channel Changes for DISPC Archit Taneja
2010-11-08 12:24 ` [PATCH v4 6/7] OMAP: DSS2: Use dss_features to handle DISPC bits removed on OMAP4 Archit Taneja
2010-11-08 12:24 ` [PATCH v4 7/7] OMAP: DSS2: Add new Overlay Manager 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=1289904957.2668.75.camel@tubuntu \
--to=tomi.valkeinen@nokia.com \
--cc=archit@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mmittal@ti.com \
--cc=samreen@ti.com \
--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