From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: exynos_defconfig: Enable HDMI support
Date: Tue, 24 Mar 2015 21:52:10 +0900 [thread overview]
Message-ID: <02b201d06631$58129d70$0837d850$@kernel.org> (raw)
In-Reply-To: <CABxcv==Ko2PUfwuo8D2JDL4iR4+VGvewQpR_RDh9pB4Qbg5c=g@mail.gmail.com>
Javier Martinez Canilla wrote:
>
> Hello Kukjin,
>
Hi,
> On Tue, Mar 17, 2015 at 7:54 PM, Javier Martinez Canillas
> <javier@dowhile0.org> wrote:
> > On Fri, Feb 6, 2015 at 6:42 PM, Javier Martinez Canillas
> > <javier.martinez@collabora.co.uk> wrote:
> >> Many Exynos boards have an HDMI port so enable Exynos DRM HDMI support.
> >>
> >> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> >> ---
> >>
> >> Exynos DRM HDMI has some issues that were fixed by Andrzej's [0] series.
> >> So now is safe to HDMI support for Exynos boards.
> >>
> >> [0]: https://lkml.org/lkml/2015/2/5/265
> >>
> >> arch/arm/configs/exynos_defconfig | 1 +
> >> 1 file changed, 1 insertion(+)
> >>
> >> diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig
> >> index 70e5d0bdb4e4..e44da52e5223 100644
> >> --- a/arch/arm/configs/exynos_defconfig
> >> +++ b/arch/arm/configs/exynos_defconfig
> >> @@ -120,6 +120,7 @@ CONFIG_REGULATOR_S2MPS11=y
> >> CONFIG_REGULATOR_S5M8767=y
> >> CONFIG_REGULATOR_TPS65090=y
> >> CONFIG_DRM=y
> >> +CONFIG_DRM_EXYNOS_HDMI=y
> >> CONFIG_DRM_BRIDGE=y
> >> CONFIG_DRM_PTN3460=y
> >> CONFIG_DRM_PS8622=y
> >> --
> >
> > It seems you missed this patch when picking the exynos_defconfig patches.
> >
>
> Another gentle reminder about this patch.
>
Thanks, will apply tonight ;-)
- Kukjin
prev parent reply other threads:[~2015-03-24 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 17:42 [PATCH 1/1] ARM: exynos_defconfig: Enable HDMI support Javier Martinez Canillas
2015-03-17 18:54 ` Javier Martinez Canillas
2015-03-24 9:03 ` Javier Martinez Canillas
2015-03-24 12:52 ` Kukjin Kim [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='02b201d06631$58129d70$0837d850$@kernel.org' \
--to=kgene@kernel.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).