Simon,
> On 06 Jun 2017, at 02:05, Simon Glass wrote:
>
> What’s the preferred way that you’d like this resolved:
> (a) wait until the HDMI-changes (in Anatolij’s tree) are merged to master,
> before applying this patch?
> (b) fix the issue in the older rk_hdmi.c (which
Hi,
On Jun 5, 2017 17:01, "Dr. Philipp Tomsich" <
philipp.toms...@theobroma-systems.com> wrote:
Simon,
This was only tested with the new RK3399 HDMI support in place.
There’s a missing #include in the original rk_hdmi.c (before I submitted my
patches for HDMI), which causes these functions to
Simon,
This was only tested with the new RK3399 HDMI support in place.
There’s a missing #include in the original rk_hdmi.c (before I submitted my
patches for HDMI), which causes these functions to not be defined.
What’s the preferred way that you’d like this resolved:
(a) wait until the
Hi Phlilpp,
On 1 June 2017 at 20:55, Simon Glass wrote:
> On 31 May 2017 at 10:18, Philipp Tomsich
> wrote:
>> With HDMI output for the RK3399 working, this update the RK3399-Q7
>> (Puma) defconfig for the new functionality:
>> 1.
On 31 May 2017 at 10:18, Philipp Tomsich
wrote:
> With HDMI output for the RK3399 working, this update the RK3399-Q7
> (Puma) defconfig for the new functionality:
> 1. enables PMIC command (to check if the HDMI voltages are correct)
>
With HDMI output for the RK3399 working, this update the RK3399-Q7
(Puma) defconfig for the new functionality:
1. enables PMIC command (to check if the HDMI voltages are correct)
+CONFIG_CMD_PMIC=y
+CONFIG_CMD_REGULATOR=y
2. enables video-output (via HDMI)
+CONFIG_DM_VIDEO=y
6 matches
Mail list logo