All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Vikas Sajjan <vikas.sajjan@linaro.org>
Cc: Tomasz Figa <t.figa@samsung.com>,
	dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org,
	inki.dae@samsung.com, tomi.valkeinen@ti.com,
	aditya.ps@samsung.com, sunil joshi <joshi@samsung.com>,
	Jesse Barker <jesse.barker@linaro.org>,
	Rob Clark <rob.clark@linaro.org>
Subject: Re: [PATCH 2/2] [RFC] video: display: Adding frame related ops to MIPI DSI video source struct
Date: Thu, 10 Jan 2013 00:35:22 +0100	[thread overview]
Message-ID: <3145597.3X0nZfdYRE@avalon> (raw)
In-Reply-To: <CAD025yQHuW3O-Wqwjjsf79UcXjxezUZEwoY-P1J5Fqb+OB+gHA@mail.gmail.com>

Hi Vikas,

Thank you for the patch.

On Friday 04 January 2013 10:24:04 Vikas Sajjan wrote:
> On 3 January 2013 16:29, Tomasz Figa <t.figa@samsung.com> wrote:
> > 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.
> 
> Right, exynos_mipi_dsi_blank_mode() only supports FB_BLANK_UNBLANK as
> of now, but FB_BLANK_NORMAL will be supported in future.
> If not for Exynos, i think it will be need for other SoCs which
> support FB_BLANK_UNBLANK and FB_BLANK_NORMAL.

Could you please explain in a bit more details what the set_early_blank_mode 
and set_blank_mode operations do ?

> > 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.
> 
> You are right, as of now Exynos MIPI DSI Panels are NOT using these
> callbacks, but as you mentioned we will need frame done status monitoring
> anyways, so i included these callbacks here. Will check, if we can implement
> any better method.

Do you expect the entity drivers (and in particular the panel drivers) to 
require frame done notification ? If so, could you explain your use case(s) ?

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2013-01-09 23:35 UTC|newest]

Thread overview: 12+ 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-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
2013-01-04  4:54     ` Vikas Sajjan
2013-01-09 23:35       ` Laurent Pinchart [this message]
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=3145597.3X0nZfdYRE@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=aditya.ps@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=inki.dae@samsung.com \
    --cc=jesse.barker@linaro.org \
    --cc=joshi@samsung.com \
    --cc=linux-media@vger.kernel.org \
    --cc=rob.clark@linaro.org \
    --cc=t.figa@samsung.com \
    --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 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.