From: Nishanth Menon <nm@ti.com>
To: "Taneja, Archit" <archit@ti.com>
Cc: "tomi.valkeinen@nokia.com" <tomi.valkeinen@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v2] OMAP: DSS2: Fix error path in omap_dsi_update()
Date: Wed, 14 Jul 2010 11:01:01 -0500 [thread overview]
Message-ID: <4C3DDF3D.7010609@ti.com> (raw)
In-Reply-To: <1279109510-12992-1-git-send-email-archit@ti.com>
Taneja, Archit had written, on 07/14/2010 07:11 AM, the following:
> In the case of an error on calling dsi_update_screen_l4(), a
> successful framedone callback is still sent to panel-taal. An
> error should be returned to taal_update() instead.
>
> Signed-off-by: Archit Taneja <archit@ti.com>
> ---
> v2: This fixes a compilation warning seen after
> builing with v1.
>
> v1:
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg31715.html
>
> drivers/video/omap2/dss/dsi.c | 7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/video/omap2/dss/dsi.c b/drivers/video/omap2/dss/dsi.c
> index a6e0f64..b3fa3a7
> --- a/drivers/video/omap2/dss/dsi.c
> +++ b/drivers/video/omap2/dss/dsi.c
> @@ -2920,7 +2920,12 @@ int omap_dsi_update(struct omap_dss_device *dssdev,
>
> dsi_update_screen_dispc(dssdev, x, y, w, h);
dont need the error check here?
> } else {
> - dsi_update_screen_l4(dssdev, x, y, w, h);
> + int r;
> +
> + r = dsi_update_screen_l4(dssdev, x, y, w, h);
> + if (r)
no print for warning developer/user? is this error expected?
> + return r;
> +
> dsi_perf_show("L4");
> callback(0, data);
> }
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2010-07-14 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 12:11 [PATCH v2] OMAP: DSS2: Fix error path in omap_dsi_update() Archit Taneja
2010-07-14 16:01 ` Nishanth Menon [this message]
2010-07-17 6:44 ` Taneja, Archit
2010-07-27 7:19 ` Tomi Valkeinen
2010-07-27 7:34 ` Taneja, Archit
2010-07-27 7:43 ` Tomi Valkeinen
2010-07-27 8:23 ` Taneja, Archit
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=4C3DDF3D.7010609@ti.com \
--to=nm@ti.com \
--cc=archit@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@nokia.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;
as well as URLs for NNTP newsgroup(s).