All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>, arm-soc <arm@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: spear3xx_defconfig: Activate PL111 DRM driver
Date: Fri, 1 Mar 2019 15:09:49 +0100	[thread overview]
Message-ID: <CAK8P3a0UC3f2fg90DH536mNuaNRzXjootBR4rs1ckqW+x=+Kdg@mail.gmail.com> (raw)
In-Reply-To: <20190225143141.2611-1-linus.walleij@linaro.org>

On Mon, Feb 25, 2019 at 3:31 PM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> This disables the old FBDEV driver and enables the PL111
> DRM driver on the SPEAr3xx.
>
> There are some device trees in the kernel that switches
> the DT node for the PL110 to "okay" but none of these
> have any display defined, so we can safely switch to this
> driver before we get any users starting to define
> displays. Let them do it on top of the new driver
> infrastructure instead.
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ARM SoC folks: please apply this directly for wherever
> defconfigs go so I can cut all ties to the old FBDEV
> driver.
> ---
>  arch/arm/configs/spear3xx_defconfig | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)

Applied into arm/defconfigs for 5.1, thanks!

     Arnd

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2019-03-01 14:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-25 14:31 [PATCH] ARM: spear3xx_defconfig: Activate PL111 DRM driver Linus Walleij
2019-03-01 14:09 ` Arnd Bergmann [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='CAK8P3a0UC3f2fg90DH536mNuaNRzXjootBR4rs1ckqW+x=+Kdg@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=arm@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=viresh.kumar@linaro.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.