linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC 1/2] ARM: multi_v7_defconfig: Make drm support modular
Date: Fri, 29 May 2015 18:33:42 +0200	[thread overview]
Message-ID: <CAMuHMdVKjgNEUot44E45Q1UWCgUC6zOM5mLhBr0qWuXRim3DsA@mail.gmail.com> (raw)
In-Reply-To: <2568731.dqdEiMuDro@wuerfel>

On Fri, May 29, 2015 at 5:41 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Friday 29 May 2015 15:25:25 Geert Uytterhoeven wrote:
>> From: Geert Uytterhoeven <geert+renesas@glider.be>
>>
>> Make drm support modular to reduce kernel size (-620 KiB):
>>
>>        text    data     bss     dec     hex   filename
>>     12211122 1392076  338520 13941718  d4bbd6 vmlinux.before
>>     11581470 1387196  338264 13306930  cb0c32 vmlinux.after
>>
>> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>> ---
>> Slightly controversial:
>>   - Does anyone need drm for boot testing?
>
> Only the tegra driver is affected, so let's ask the tegra
> maintainers.

And the qcom maintainers.

CONFIG_DRM_MSM also changes from m to y, but this is not visible in
multi_v7_defconfig due to CONFIG_DRM_MSM_FBDEV=y and defconfig reduction...

>>  arch/arm/configs/multi_v7_defconfig | 8 +++++---
>>  1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
>> index 40ca1ab29a2e350f..9b4e33d5b15e340f 100644
>> --- a/arch/arm/configs/multi_v7_defconfig
>> +++ b/arch/arm/configs/multi_v7_defconfig
>> @@ -426,15 +426,17 @@ CONFIG_VIDEO_RENESAS_VSP1=m
>>  # CONFIG_MEDIA_SUBDRV_AUTOSELECT is not set
>>  CONFIG_VIDEO_ADV7180=m
>>  CONFIG_VIDEO_ML86V7667=m
>> -CONFIG_DRM=y
>> +CONFIG_TEGRA_HOST1X=y
>> +CONFIG_DRM=m
>>  CONFIG_DRM_PTN3460=m
>>  CONFIG_DRM_PS8622=m
>>  CONFIG_DRM_EXYNOS=m
>>  CONFIG_DRM_EXYNOS_FIMD=y
>>  CONFIG_DRM_EXYNOS_HDMI=y
>>  CONFIG_DRM_RCAR_DU=m
>> -CONFIG_DRM_TEGRA=y
>> -CONFIG_DRM_PANEL_SIMPLE=y
>> +CONFIG_DRM_TEGRA=m
>> +CONFIG_DRM_PANEL_SIMPLE=m
>> +CONFIG_FB=y
>>  CONFIG_FB_ARMCLCD=y
>>  CONFIG_FB_WM8505=y
>>  CONFIG_FB_SH_MOBILE_LCDC=y

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2015-05-29 16:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29 13:25 [PATCH/RFC 1/2] ARM: multi_v7_defconfig: Make drm support modular Geert Uytterhoeven
2015-05-29 13:25 ` [PATCH/RFC 2/2] ARM: multi_v7_defconfig: Make fbdev " Geert Uytterhoeven
2015-05-29 14:31   ` Arnd Bergmann
2015-05-29 15:41 ` [PATCH/RFC 1/2] ARM: multi_v7_defconfig: Make drm " Arnd Bergmann
2015-05-29 16:33   ` Geert Uytterhoeven [this message]
2015-06-05 11:39   ` Thierry Reding
2015-06-08  2:09     ` Alexandre Courbot

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=CAMuHMdVKjgNEUot44E45Q1UWCgUC6zOM5mLhBr0qWuXRim3DsA@mail.gmail.com \
    --to=geert@linux-m68k.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 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).