public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Sandy Huang <hjc@rock-chips.com>
Cc: seanpaul@chromium.org, linux-rockchip@lists.infradead.org,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/3] Add support rockchip RGB output interface
Date: Thu, 30 Aug 2018 10:28:16 +0200	[thread overview]
Message-ID: <38391933.H7ebZMqo79@phil> (raw)
In-Reply-To: <1535512364-80764-1-git-send-email-hjc@rock-chips.com>

Am Mittwoch, 29. August 2018, 05:12:41 CEST schrieb Sandy Huang:
> This patches add support rockchip RGB output, Some Rockchip CRTCs, like
> rv1108 and px30 can directly output parallel and serial RGB data to panel
> or to conversion chip.
> So add a feature-bit for vops to mark the ability for these direct outputs
> and add an internal encoder in that case, that can attach to bridge chips
> or panels.

I'm obviously ok with this series, but let's give it till monday or so
before applying to give people a bit longer to comment if necessary.


Heiko



      parent reply	other threads:[~2018-08-30  8:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29  3:12 [PATCH v7 0/3] Add support rockchip RGB output interface Sandy Huang
2018-08-29  3:12 ` [PATCH v7 1/3] drm/tockchip: add function to check if endpoint is a subdriver Sandy Huang
2018-08-29  3:12 ` [PATCH v7 2/3] drm/rockchip: Add support for Rockchip Soc RGB output interface Sandy Huang
2018-08-29  3:12 ` [PATCH v7 3/3] drm/rockchip: Add directly output rgb feature for px30 Sandy Huang
2018-08-30  8:28 ` Heiko Stuebner [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=38391933.H7ebZMqo79@phil \
    --to=heiko@sntech.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hjc@rock-chips.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=seanpaul@chromium.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