All of lore.kernel.org
 help / color / mirror / Atom feed
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 v5] drm/pl111: Support the Versatile Express
Date: Thu, 3 May 2018 11:58:38 +0200	[thread overview]
Message-ID: <CACRpkdZK8ahaWT1Y4jQ_W6pkUZeGSFP4BT8DgtvBAKb=vX1cfA@mail.gmail.com> (raw)
In-Reply-To: <20180503094144.GK12521@phenom.ffwll.local>

On Thu, May 3, 2018 at 11:41 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
>Me:
(...)
>> ChangeLog v4->v5:
>> - Collect Robin's Tested-by
>> - Switch to builtin_platform_driver() for the muxfpga as this
>>   file is always built as "-y" for the arch and we need to
>>   avoid module collisions with the main PL111 driver.
>> +builtin_platform_driver(vexpress_muxfpga_driver);
>
>   LD [M]  drivers/gpu/drm/pl111/pl111_drm.o
> drivers/gpu/drm/pl111/pl111_vexpress.o: In function `vexpress_muxfpga_driver_init':
> /home/daniel/linux/aarch64/drivers/gpu/drm/pl111/pl111_vexpress.c:125: multiple definition of `init_module'
> drivers/gpu/drm/pl111/pl111_drv.o:/home/daniel/linux/aarch64/drivers/gpu/drm/pl111/pl111_drv.c:427: first defined here
> make[4]: *** [scripts/Makefile.build:570: drivers/gpu/drm/pl111/pl111_drm.o] Error 1
> make[3]: *** [scripts/Makefile.build:583: drivers/gpu/drm/pl111] Error 2
> make[3]: *** Waiting for unfinished jobs....
>
> Using the default drm-misc configs.
>
> Please fix asap, and please compile-test before pushing using these
> default configs so others aren't blocked. I've disabled the pl111 driver
> in there for now, please also re-enable.

That's typical. As you see in the ChangeLog I really tried to address
exactly this. I got that build error from the zeroday build with v4,
changed it to a builtin driver and pushed, then it did not give me
the problem again.

I guess the zeroday build robot isn't using the same configs...

Hm, I will take suggestions on how to actually solve it, I guess
this is due to the initcall infrastructure only allowing one initcall
per module?

In that case I guess I should either:
- Break out the vexpress file into its own module
- Call the vexpress init hooks from the initcalls in the
  main module

I guess I will go for the latter even if it litters the driver with
more cross-calls.

Yours,
Linus Walleij

WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Pawel Moll <pawel.moll@arm.com>,
	Liviu Dudau <liviu.dudau@arm.com>,
	"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2 v5] drm/pl111: Support the Versatile Express
Date: Thu, 3 May 2018 11:58:38 +0200	[thread overview]
Message-ID: <CACRpkdZK8ahaWT1Y4jQ_W6pkUZeGSFP4BT8DgtvBAKb=vX1cfA@mail.gmail.com> (raw)
In-Reply-To: <20180503094144.GK12521@phenom.ffwll.local>

On Thu, May 3, 2018 at 11:41 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
>Me:
(...)
>> ChangeLog v4->v5:
>> - Collect Robin's Tested-by
>> - Switch to builtin_platform_driver() for the muxfpga as this
>>   file is always built as "-y" for the arch and we need to
>>   avoid module collisions with the main PL111 driver.
>> +builtin_platform_driver(vexpress_muxfpga_driver);
>
>   LD [M]  drivers/gpu/drm/pl111/pl111_drm.o
> drivers/gpu/drm/pl111/pl111_vexpress.o: In function `vexpress_muxfpga_driver_init':
> /home/daniel/linux/aarch64/drivers/gpu/drm/pl111/pl111_vexpress.c:125: multiple definition of `init_module'
> drivers/gpu/drm/pl111/pl111_drv.o:/home/daniel/linux/aarch64/drivers/gpu/drm/pl111/pl111_drv.c:427: first defined here
> make[4]: *** [scripts/Makefile.build:570: drivers/gpu/drm/pl111/pl111_drm.o] Error 1
> make[3]: *** [scripts/Makefile.build:583: drivers/gpu/drm/pl111] Error 2
> make[3]: *** Waiting for unfinished jobs....
>
> Using the default drm-misc configs.
>
> Please fix asap, and please compile-test before pushing using these
> default configs so others aren't blocked. I've disabled the pl111 driver
> in there for now, please also re-enable.

That's typical. As you see in the ChangeLog I really tried to address
exactly this. I got that build error from the zeroday build with v4,
changed it to a builtin driver and pushed, then it did not give me
the problem again.

I guess the zeroday build robot isn't using the same configs...

Hm, I will take suggestions on how to actually solve it, I guess
this is due to the initcall infrastructure only allowing one initcall
per module?

In that case I guess I should either:
- Break out the vexpress file into its own module
- Call the vexpress init hooks from the initcalls in the
  main module

I guess I will go for the latter even if it litters the driver with
more cross-calls.

Yours,
Linus Walleij
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-05-03  9:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 13:47 [PATCH 1/2 v5] drm/pl111: Support the Versatile Express Linus Walleij
2018-05-02 13:47 ` Linus Walleij
2018-05-02 13:47 ` [PATCH 2/2 v5] drm/pl111: Enable device-specific assigned memory Linus Walleij
2018-05-02 13:47   ` Linus Walleij
2018-05-03  9:41 ` [PATCH 1/2 v5] drm/pl111: Support the Versatile Express Daniel Vetter
2018-05-03  9:41   ` Daniel Vetter
2018-05-03  9:58   ` Linus Walleij [this message]
2018-05-03  9:58     ` Linus Walleij
2018-05-03 10:41     ` Daniel Vetter
2018-05-03 10:41       ` Daniel Vetter

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='CACRpkdZK8ahaWT1Y4jQ_W6pkUZeGSFP4BT8DgtvBAKb=vX1cfA@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.