From: Archit Taneja <a0393947@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 12/17] OMAPDSS: clean up dss_mgr_set_timings
Date: Fri, 07 Sep 2012 11:48:58 +0000 [thread overview]
Message-ID: <5049DC5A.1060601@ti.com> (raw)
In-Reply-To: <1347012673.2646.3.camel@deskari>
On Friday 07 September 2012 03:41 PM, Tomi Valkeinen wrote:
> On Wed, 2012-09-05 at 11:25 +0300, Tomi Valkeinen wrote:
>> dss_mgr_set_timings() can only be called when the output is not active.
>> This means that most of the code in the function is extra, as there's no
>> need to write the values to registers, etc, because that will be handled
>> when the output will be enabled.
>>
>> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
>> ---
>> drivers/video/omap2/dss/apply.c | 18 ++++++++----------
>> 1 file changed, 8 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/video/omap2/dss/apply.c b/drivers/video/omap2/dss/apply.c
>> index 53629dd..1b49019 100644
>> --- a/drivers/video/omap2/dss/apply.c
>> +++ b/drivers/video/omap2/dss/apply.c
>> @@ -1314,21 +1314,19 @@ void dss_mgr_set_timings(struct omap_overlay_manager *mgr,
>> const struct omap_video_timings *timings)
>> {
>> unsigned long flags;
>> -
>> - mutex_lock(&apply_lock);
>> + struct mgr_priv_data *mp = get_mgr_priv(mgr);
>>
>> spin_lock_irqsave(&data_lock, flags);
>>
>> - dss_apply_mgr_timings(mgr, timings);
>> -
>> - dss_write_regs();
>> - dss_set_go_bits();
>> + if (mp->enabled) {
>> + DSSERR("cannot set timings for %s: manager needs to be disabled\n",
>> + mgr->name);
>> + goto out;
>> + }
>
> There was a problem with this one. When using manual update display, we
> call set_timings before each update, and the mgr is enabled at that
> time.
>
> I'll fix this by changing the check from mp->enabled to mp->updating.
> That flag tells if the DISPC channel is actually enabled or not. Enabled
> flag just tells that the channel is being reserved, although for auto
> update displays that also implies "updating".
>
> But do you see any reason to call set_timings before each update? It was
> required when we have partial update support, but now we support only
> full screen updates, so isn't it enough to set the timings just once
> when configuring?
I think we put it there for rotation. We may need to swap manager width
and height before an update.
Archit
next prev parent reply other threads:[~2012-09-07 11:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 8:25 [PATCH 00/17] Misc OMAP DSS patches part 2 Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 01/17] OMAPDSS: Taal: use devm_* functions Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 02/17] OMAPFB1: remove unnecessary includes Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 03/17] OMAPFB1: remove a non-used table Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 04/17] OMAPDSS: remove unnecessary includes Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 05/17] OMAPFB: clear framebuffers with CPU Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 06/17] OMAPDSS: VRAM: Remove clearing with sDMA Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 07/17] OMAPDSS: Taal: Reogranize for device tree Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 08/17] OMAPDSS: TFP410: use devm_gpio_request_one Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 09/17] OMAPDSS: split overlay sysfs code Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 10/17] OMAPDSS: split manager " Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 11/17] OMAPDSS: clean up dss_mgr_set_lcd_config Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 12/17] OMAPDSS: clean up dss_mgr_set_timings Tomi Valkeinen
2012-09-05 9:27 ` Archit Taneja
2012-09-05 10:41 ` Tomi Valkeinen
2012-09-05 11:46 ` Archit Taneja
2012-09-05 11:41 ` Tomi Valkeinen
2012-09-05 11:48 ` Archit Taneja
2012-09-07 10:11 ` Tomi Valkeinen
2012-09-07 11:48 ` Archit Taneja [this message]
2012-09-05 8:25 ` [PATCH 13/17] Revert "OMAPDSS: APPLY: add fifo-merge support" Tomi Valkeinen
2012-09-05 13:55 ` Archit Taneja
2012-09-06 12:55 ` Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 14/17] Revert "OMAPDSS: APPLY: add fifo merge support funcs" Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 15/17] OMAPDSS: remove extra_info completion code Tomi Valkeinen
2012-09-05 13:43 ` Archit Taneja
2012-09-06 13:04 ` Tomi Valkeinen
2012-09-06 13:47 ` Archit Taneja
2012-09-06 13:42 ` Tomi Valkeinen
2012-09-06 14:13 ` Archit Taneja
2012-09-06 14:29 ` Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 16/17] OMAPDSS: Improve fifo management code Tomi Valkeinen
2012-09-05 8:25 ` [PATCH 17/17] OMAPDSS: Use WB fifo for GFX overlay Tomi Valkeinen
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=5049DC5A.1060601@ti.com \
--to=a0393947@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@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;
as well as URLs for NNTP newsgroup(s).