Linux-Rockchip Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Jagan Teki <jagan@amarulasolutions.com>,
	Anatolij Gustschin <agust@denx.de>
Cc: "open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	U-Boot-Denx <u-boot@lists.denx.de>,
	linux-amarula <linux-amarula@amarulasolutions.com>
Subject: Re: [PATCH 4/4] rockchip: Enable HDMI output on rk3399 board w/ HDMI
Date: Mon, 3 Feb 2020 09:47:08 -0500	[thread overview]
Message-ID: <20200203144708.GK13379@bill-the-cat> (raw)
In-Reply-To: <CAMty3ZBQ_mRY4ojo_4iHUzup2tD-FO6ZmskwJyXskg4O4iHz+Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4629 bytes --]

On Mon, Feb 03, 2020 at 04:55:27PM +0530, Jagan Teki wrote:
> On Fri, Jan 24, 2020 at 8:57 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > On Thu, Jan 23, 2020 at 09:58:45PM +0530, Jagan Teki wrote:
> >
> > > Enable config options and console setting to respective
> > > rk3399 board for HDMI output.
> > >
> > > Boards supported and tested on this patch are:
> > > - NanoPc T4
> > > - NanoPi M4
> > > - NanoPi Neo4
> > > - ROC-RK3399-PC
> > >
> > > Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> > > ---
> > >  configs/nanopc-t4-rk3399_defconfig   | 6 ++++++
> > >  configs/nanopi-m4-rk3399_defconfig   | 6 ++++++
> > >  configs/nanopi-neo4-rk3399_defconfig | 6 ++++++
> > >  configs/roc-pc-rk3399_defconfig      | 6 ++++++
> > >  include/configs/evb_rk3399.h         | 5 +++++
> > >  5 files changed, 29 insertions(+)
> > >
> > > diff --git a/configs/nanopc-t4-rk3399_defconfig b/configs/nanopc-t4-rk3399_defconfig
> > > index bd6d60ff6c..17e8a18d31 100644
> > > --- a/configs/nanopc-t4-rk3399_defconfig
> > > +++ b/configs/nanopc-t4-rk3399_defconfig
> > > @@ -53,3 +53,9 @@ CONFIG_USB_ETHER_RTL8152=y
> > >  CONFIG_USB_ETHER_SMSC95XX=y
> > >  CONFIG_SPL_TINY_MEMSET=y
> > >  CONFIG_ERRNO_STR=y
> > > +CONFIG_DM_VIDEO=y
> > > +CONFIG_VIDEO_BPP16=y
> > > +CONFIG_VIDEO_BPP32=y
> > > +CONFIG_DISPLAY=y
> > > +CONFIG_VIDEO_ROCKCHIP=y
> > > +CONFIG_DISPLAY_ROCKCHIP_HDMI=y
> > > diff --git a/configs/nanopi-m4-rk3399_defconfig b/configs/nanopi-m4-rk3399_defconfig
> > > index 74ede13c23..b73b2fdc27 100644
> > > --- a/configs/nanopi-m4-rk3399_defconfig
> > > +++ b/configs/nanopi-m4-rk3399_defconfig
> > > @@ -53,3 +53,9 @@ CONFIG_USB_ETHER_RTL8152=y
> > >  CONFIG_USB_ETHER_SMSC95XX=y
> > >  CONFIG_SPL_TINY_MEMSET=y
> > >  CONFIG_ERRNO_STR=y
> > > +CONFIG_DM_VIDEO=y
> > > +CONFIG_VIDEO_BPP16=y
> > > +CONFIG_VIDEO_BPP32=y
> > > +CONFIG_DISPLAY=y
> > > +CONFIG_VIDEO_ROCKCHIP=y
> > > +CONFIG_DISPLAY_ROCKCHIP_HDMI=y
> > > diff --git a/configs/nanopi-neo4-rk3399_defconfig b/configs/nanopi-neo4-rk3399_defconfig
> > > index a44124aac0..2ecb50967b 100644
> > > --- a/configs/nanopi-neo4-rk3399_defconfig
> > > +++ b/configs/nanopi-neo4-rk3399_defconfig
> > > @@ -53,3 +53,9 @@ CONFIG_USB_ETHER_RTL8152=y
> > >  CONFIG_USB_ETHER_SMSC95XX=y
> > >  CONFIG_SPL_TINY_MEMSET=y
> > >  CONFIG_ERRNO_STR=y
> > > +CONFIG_DM_VIDEO=y
> > > +CONFIG_VIDEO_BPP16=y
> > > +CONFIG_VIDEO_BPP32=y
> > > +CONFIG_DISPLAY=y
> > > +CONFIG_VIDEO_ROCKCHIP=y
> > > +CONFIG_DISPLAY_ROCKCHIP_HDMI=y
> > > diff --git a/configs/roc-pc-rk3399_defconfig b/configs/roc-pc-rk3399_defconfig
> > > index 3a051d9b0c..a9f99f992d 100644
> > > --- a/configs/roc-pc-rk3399_defconfig
> > > +++ b/configs/roc-pc-rk3399_defconfig
> > > @@ -56,3 +56,9 @@ CONFIG_USB_ETHER_RTL8152=y
> > >  CONFIG_USB_ETHER_SMSC95XX=y
> > >  CONFIG_SPL_TINY_MEMSET=y
> > >  CONFIG_ERRNO_STR=y
> > > +CONFIG_DM_VIDEO=y
> > > +CONFIG_VIDEO_BPP16=y
> > > +CONFIG_VIDEO_BPP32=y
> > > +CONFIG_DISPLAY=y
> > > +CONFIG_VIDEO_ROCKCHIP=y
> > > +CONFIG_DISPLAY_ROCKCHIP_HDMI=y
> > > diff --git a/include/configs/evb_rk3399.h b/include/configs/evb_rk3399.h
> > > index c0b0358893..09eb361655 100644
> > > --- a/include/configs/evb_rk3399.h
> > > +++ b/include/configs/evb_rk3399.h
> > > @@ -6,6 +6,11 @@
> > >  #ifndef __EVB_RK3399_H
> > >  #define __EVB_RK3399_H
> > >
> > > +#define ROCKCHIP_DEVICE_SETTINGS \
> > > +             "stdin=serial,cros-ec-keyb\0" \
> > > +             "stdout=serial,vidconsole\0" \
> > > +             "stderr=serial,vidconsole\0"
> > > +
> > >  #include <configs/rk3399_common.h>
> > >
> > >  #if defined(CONFIG_ENV_IS_IN_MMC)
> >
> > This seems like another commit (along with the question I saw about
> > i.MX FB not showing the right colors) 2cc393f32fd9 needs to be reworked
> > so that we default to enabling everything still but let boards opt out
> > rather than forcing everyone to opt-in as it seems like there's a lot of
> > cases where people need to opt-in and didn't know.
> 
> yes, this evb board config is common across most of the rk3399
> defconfig boards. this patch enable hdmi on few rk3399 boards all use
> same config file, evb_rk3399.h

Yes, the ROCKCHIP_DEVICE_SETTINGS part makes sense, but the rest looks
very much like part of we need to rework the commit I mentioned.  I
don't object to this going in as-is.  Anatolij, how goes the rework of
things however?  I do want to see that get in sooner rather than later
so we can sort out other regressions from just a lack of CONFIG options
being enabled.  Thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-02-03 14:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23 16:28 [PATCH 0/4] rockchip: rk3399: Fix HDMI out Jagan Teki
     [not found] ` <20200123162845.10651-1-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2020-01-23 16:28   ` [PATCH 1/4] arm64: dts: rk3399-u-boot: Delete vop assigned-clocks/rates Jagan Teki
2020-01-23 16:28   ` [PATCH 2/4] video: rockchip: Fix vop modes for rk3399 Jagan Teki
2020-01-23 16:28   ` [PATCH 3/4] rockchip: Enable pre console " Jagan Teki
2020-01-23 16:28   ` [PATCH 4/4] rockchip: Enable HDMI output on rk3399 board w/ HDMI Jagan Teki
2020-01-24 15:27     ` Tom Rini
2020-01-24 17:03       ` Anatolij Gustschin
2020-02-03 11:25       ` Jagan Teki
2020-02-03 14:47         ` Tom Rini [this message]
2020-02-03 22:10           ` Anatolij Gustschin
2020-03-02 13:01     ` Peter Robinson

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=20200203144708.GK13379@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=agust@denx.de \
    --cc=jagan@amarulasolutions.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=u-boot@lists.denx.de \
    /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