linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Archit Taneja <archit@ti.com>, Benoit Cousson <b-cousson@ti.com>,
	linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: OMAP DSS warning in apply.c
Date: Tue, 14 Feb 2012 12:57:49 +0000	[thread overview]
Message-ID: <1329224269.1845.99.camel@deskari> (raw)
In-Reply-To: <20120214120643.GH15338@n2100.arm.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]

On Tue, 2012-02-14 at 12:06 +0000, Russell King - ARM Linux wrote:
> kautobuildv2 discovered this in its omap4430sdp oldconfig build:
> 
> drivers/video/omap2/dss/apply.c:350: warning: 'wait_pending_extra_info_updates' defined but not used
> 
> This looks like a valid warning, because wait_pending_extra_info_updates()
> seems to be completely unreferenced.  Should the function be removed?
> It looks like extra_updated_completion can also be removed as well, as
> that function is the only place it gets initialized and waited for.

The function will be used when the fifo merge series goes in in the next
merge window.

I added the "extra_info" code before fifo merge, as it's will be used by
the fifo merge code and it kinda belonged with the other apply stuff.

The fifo merge code was also supposed to go in in the previous merge
window with the rest of the rewrites, but due to some complications it
was delayed and missed the merge window.

> The function also looks weird - it calls extra_info_update_ongoing() first
> under a lock, and then outside the lock.  It's not particularly nice API
> wise to have stuff sometimes called under a lock and sometimes not.

The second call is actually extra, it was just added for verification
purposes during development to ensure that the wait logic works
correctly.

I'll remove it.

 Tomi


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2012-02-14 12:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14 12:06 OMAP DSS warning in apply.c Russell King - ARM Linux
2012-02-14 12:38 ` Cousson, Benoit
2012-02-14 12:57 ` Tomi Valkeinen [this message]

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=1329224269.1845.99.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=archit@ti.com \
    --cc=b-cousson@ti.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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).