mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: drm/vc4: v3d: called object '0u' is not a function (next-20160104)
Date: Tue, 05 Jan 2016 11:09:30 -0800	[thread overview]
Message-ID: <87fuybrggl.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <77332174.321557.7beec130-60c3-486d-88cc-f6686a848042.open-xchange@email.1und1.de>

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

Stefan Wahren <stefan.wahren@i2se.com> writes:

> Hi Eric,
>
> i tried to build Linux next-20160104, but vc4 failed with the following
> messages:
>
> ...
>   CC      drivers/gpu/drm/vc4/vc4_v3d.o
> drivers/gpu/drm/vc4/vc4_v3d.c: In function 'vc4_v3d_set_power':
> drivers/gpu/drm/vc4/vc4_v3d.c:157:29: error: called object '0u' is not a
> function
> drivers/gpu/drm/vc4/vc4_v3d.c:159:27: error: called object '0u' is not a
> function
> drivers/gpu/drm/vc4/vc4_v3d.c:160:1: warning: control reaches end of non-void
> function [-Wreturn-type]
> make[4]: *** [drivers/gpu/drm/vc4/vc4_v3d.o] Error 1
> make[3]: *** [drivers/gpu/drm/vc4] Error 2
> make[2]: *** [drivers/gpu/drm] Error 2
> make[1]: *** [drivers/gpu] Error 2
> make: *** [drivers] Error 2
>
> Here the relevant settings:
>
> CONFIG_DRM_VC4=y
> CONFIG_PM_SLEEP=n
>
> It looks like pm_generic_poweroff and pm_generic_resume aren't used as intended.
> They could be NULL.

http://lists.freedesktop.org/archives/dri-devel/2015-December/097509.html

Sadly, the genpd stuff didn't actually work for reset like I thought it
would.  That means reset is broken upstream, for now.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

      reply	other threads:[~2016-01-05 19:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 21:10 Stefan Wahren
2016-01-05 19:09 ` Eric Anholt [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=87fuybrggl.fsf@eliezer.anholt.net \
    --to=eric@anholt.net \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefan.wahren@i2se.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

all inboxes | Powered by JetHome®