Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1301101 > unrolled thread

drm/vc4: v3d: called object '0u' is not a function (next-20160104)

Started byStefan Wahren <stefan.wahren@i2se.com>
First post2016-01-04 22:20 +0100
Last post2016-01-05 20:10 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.kernel


Contents

  drm/vc4: v3d: called object '0u' is not a function (next-20160104) Stefan Wahren <stefan.wahren@i2se.com> - 2016-01-04 22:20 +0100
    Re: drm/vc4: v3d: called object '0u' is not a function (next-20160104) Eric Anholt <eric@anholt.net> - 2016-01-05 20:10 +0100

#1301101 — drm/vc4: v3d: called object '0u' is not a function (next-20160104)

FromStefan Wahren <stefan.wahren@i2se.com>
Date2016-01-04 22:20 +0100
Subjectdrm/vc4: v3d: called object '0u' is not a function (next-20160104)
Message-ID<qNkHM-sc-3@gated-at.bofh.it>
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.

Regards
Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1301905

FromEric Anholt <eric@anholt.net>
Date2016-01-05 20:10 +0100
Message-ID<qNF9x-77Z-51@gated-at.bofh.it>
In reply to#1301101

[Multipart message — attachments visible in raw view] — view raw

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.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web