From: Tomasz Figa <t.figa@samsung.com>
To: dri-devel@lists.freedesktop.org
Cc: Vikas C Sajjan <vikas.sajjan@linaro.org>,
linux-media@vger.kernel.org, tomi.valkeinen@ti.com,
laurent.pinchart@ideasonboard.com, aditya.ps@samsung.com
Subject: Re: [PATCH 2/2] [RFC] video: display: Adding frame related ops to MIPI DSI video source struct
Date: Thu, 03 Jan 2013 11:59:13 +0100 [thread overview]
Message-ID: <67872310.6yRVsVsClR@amdc1227> (raw)
In-Reply-To: <1357132642-24588-3-git-send-email-vikas.sajjan@linaro.org>
Hi Vikas,
On Wednesday 02 of January 2013 18:47:22 Vikas C Sajjan wrote:
> From: Vikas Sajjan <vikas.sajjan@linaro.org>
>
> Signed-off-by: Vikas Sajjan <vikas.sajjan@linaro.org>
> ---
> include/video/display.h | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/include/video/display.h b/include/video/display.h
> index b639fd0..fb2f437 100644
> --- a/include/video/display.h
> +++ b/include/video/display.h
> @@ -117,6 +117,12 @@ struct dsi_video_source_ops {
>
> void (*enable_hs)(struct video_source *src, bool enable);
>
> + /* frame related */
> + int (*get_frame_done)(struct video_source *src);
> + int (*clear_frame_done)(struct video_source *src);
> + int (*set_early_blank_mode)(struct video_source *src, int power);
> + int (*set_blank_mode)(struct video_source *src, int power);
> +
I'm not sure if all those extra ops are needed in any way.
Looking and Exynos MIPI DSIM driver, set_blank_mode is handling only
FB_BLANK_UNBLANK status, which basically equals to the already existing
enable operation, while set_early_blank mode handles only
FB_BLANK_POWERDOWN, being equal to disable callback.
Both get_frame_done and clear_frame_done do not look at anything used at
the moment and if frame done status monitoring will be ever needed, I
think a better way should be implemented.
Best regards,
--
Tomasz Figa
Samsung Poland R&D Center
SW Solution Development, Linux Platform
next prev parent reply other threads:[~2013-01-03 10:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 13:17 [PATCH 0/2] Making Exynos MIPI Complaint with Common Display Framework Vikas C Sajjan
2013-01-02 13:17 ` [PATCH 1/2] [RFC] video: exynos mipi dsi: Making Exynos MIPI Complaint with CDF Vikas C Sajjan
2013-01-03 5:44 ` Sachin Kamat
2013-01-03 8:30 ` Vikas Sajjan
2013-01-02 13:17 ` [PATCH 2/2] [RFC] video: display: Adding frame related ops to MIPI DSI video source struct Vikas C Sajjan
2013-01-03 10:59 ` Tomasz Figa [this message]
2013-01-04 4:54 ` Vikas Sajjan
2013-01-09 23:35 ` Laurent Pinchart
2013-01-10 5:37 ` Vikas Sajjan
2013-01-10 7:43 ` Inki Dae
2013-01-10 11:33 ` Jani Nikula
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=67872310.6yRVsVsClR@amdc1227 \
--to=t.figa@samsung.com \
--cc=aditya.ps@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=vikas.sajjan@linaro.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