From: Heiko Stuebner <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org
Cc: robin.murphy@arm.com, hjc@rock-chips.com,
linux-arm-kernel@lists.infradead.org, zhengyang@rock-chips.com
Subject: Re: [PATCH v3 0/4] rk3328 and rock64 display support
Date: Fri, 28 Sep 2018 16:06:31 +0200 [thread overview]
Message-ID: <4674830.T5MsTfmpAf@phil> (raw)
In-Reply-To: <20180910092843.1700-1-heiko@sntech.de>
Am Montag, 10. September 2018, 11:28:39 CEST schrieb Heiko Stuebner:
> Companion series for the display modifications adding the necessary
> devicetree stuff for display support on the rk3328-rock64.
>
> changes in v3:
> - drop reg from hdmi port - unneeded with a single vop
> as suggested by Robin
>
> changes in v2:
> - add defconfig addition for the phy driver
> - adapt to changed reference clock names
> - remove trailing 0 from vop irq
>
> Heiko Stuebner (4):
> arm64: dts: rockchip: add Innosilicon hdmi phy node to rk3328
> arm64: dts: rockchip: add rk3328 display nodes
> arm64: dts: rockchip: enable display nodes on rk3328-rock64
> arm64: defconfig: enable Rockchip Innosilicon hdmiphy
with phy and hdmi support being scheduled for 4.20,
applied these as well.
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] rk3328 and rock64 display support
Date: Fri, 28 Sep 2018 16:06:31 +0200 [thread overview]
Message-ID: <4674830.T5MsTfmpAf@phil> (raw)
In-Reply-To: <20180910092843.1700-1-heiko@sntech.de>
Am Montag, 10. September 2018, 11:28:39 CEST schrieb Heiko Stuebner:
> Companion series for the display modifications adding the necessary
> devicetree stuff for display support on the rk3328-rock64.
>
> changes in v3:
> - drop reg from hdmi port - unneeded with a single vop
> as suggested by Robin
>
> changes in v2:
> - add defconfig addition for the phy driver
> - adapt to changed reference clock names
> - remove trailing 0 from vop irq
>
> Heiko Stuebner (4):
> arm64: dts: rockchip: add Innosilicon hdmi phy node to rk3328
> arm64: dts: rockchip: add rk3328 display nodes
> arm64: dts: rockchip: enable display nodes on rk3328-rock64
> arm64: defconfig: enable Rockchip Innosilicon hdmiphy
with phy and hdmi support being scheduled for 4.20,
applied these as well.
next prev parent reply other threads:[~2018-09-28 14:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 9:28 [PATCH v3 0/4] rk3328 and rock64 display support Heiko Stuebner
2018-09-10 9:28 ` Heiko Stuebner
2018-09-10 9:28 ` [PATCH v3 1/4] arm64: dts: rockchip: add Innosilicon hdmi phy node to rk3328 Heiko Stuebner
2018-09-10 9:28 ` Heiko Stuebner
[not found] ` <20180910092843.1700-1-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2018-09-10 9:28 ` [PATCH v3 2/4] arm64: dts: rockchip: add rk3328 display nodes Heiko Stuebner
2018-09-10 9:28 ` Heiko Stuebner
2018-09-10 9:28 ` [PATCH v3 3/4] arm64: dts: rockchip: enable display nodes on rk3328-rock64 Heiko Stuebner
2018-09-10 9:28 ` Heiko Stuebner
2018-09-10 9:28 ` [PATCH v3 4/4] arm64: defconfig: enable Rockchip Innosilicon hdmiphy Heiko Stuebner
2018-09-10 9:28 ` Heiko Stuebner
2018-09-28 14:06 ` Heiko Stuebner [this message]
2018-09-28 14:06 ` [PATCH v3 0/4] rk3328 and rock64 display support Heiko Stuebner
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=4674830.T5MsTfmpAf@phil \
--to=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robin.murphy@arm.com \
--cc=zhengyang@rock-chips.com \
/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.