public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel•org>
To: Justin Swartz <justin.swartz@risingedge•co.za>
Cc: "Mark Rutland" <mark.rutland@arm•com>,
	devicetree@vger•kernel.org,
	"Justin Swartz" <justin.swartz@risingedge•co.za>,
	"Heiko Stübner" <heiko@sntech•de>,
	"David Airlie" <airlied@linux•ie>,
	"Sandy Huang" <hjc@rock-chips•com>,
	dri-devel@lists•freedesktop.org, linux-kernel@vger•kernel.org,
	linux-rockchip@lists•infradead.org,
	"Daniel Vetter" <daniel@ffwll•ch>,
	linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH] drm/rockchip: dw_hdmi: add basic rk3228 support
Date: Fri, 14 Jun 2019 10:47:02 -0600	[thread overview]
Message-ID: <20190614164702.GA20322@bogus> (raw)
In-Reply-To: <20190522224631.25164-1-justin.swartz@risingedge.co.za>

On Wed, 22 May 2019 22:46:29 +0000, Justin Swartz wrote:
> Like the RK3328, RK322x SoCs offer a Synopsis DesignWare HDMI transmitter
> and an Innosilicon HDMI PHY.
> 
> Add a new dw_hdmi_plat_data struct, rk3228_hdmi_drv_data.
> Assign a set of mostly generic rk3228_hdmi_phy_ops functions.
> Add dw_hdmi_rk3228_setup_hpd() to enable the HDMI HPD and DDC lines.
> 
> Signed-off-by: Justin Swartz <justin.swartz@risingedge•co.za>
> ---
>  .../bindings/display/rockchip/dw_hdmi-rockchip.txt |  1 +
>  drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c        | 53 ++++++++++++++++++++++
>  2 files changed, 54 insertions(+)
> 

Reviewed-by: Rob Herring <robh@kernel•org>

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

      parent reply	other threads:[~2019-06-14 16:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 22:46 [PATCH] drm/rockchip: dw_hdmi: add basic rk3228 support Justin Swartz
2019-06-14 12:04 ` Heiko Stuebner
2019-06-14 16:47 ` Rob Herring [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=20190614164702.GA20322@bogus \
    --to=robh@kernel$(echo .)org \
    --cc=airlied@linux$(echo .)ie \
    --cc=daniel@ffwll$(echo .)ch \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=dri-devel@lists$(echo .)freedesktop.org \
    --cc=heiko@sntech$(echo .)de \
    --cc=hjc@rock-chips$(echo .)com \
    --cc=justin.swartz@risingedge$(echo .)co.za \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-rockchip@lists$(echo .)infradead.org \
    --cc=mark.rutland@arm$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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