From: Heiko Stuebner <heiko@sntech.de>
To: agajjar <Akash_Gajjar@mentor.com>
Cc: Oskari Lemmela <oskari@lemmela.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: rockpro64 fix video output chain
Date: Thu, 06 Dec 2018 14:03:27 +0100 [thread overview]
Message-ID: <3141294.pN5WgFrMoD@phil> (raw)
In-Reply-To: <09287391-d541-cddb-4168-55ca6fee3f16@mentor.com>
Am Mittwoch, 5. Dezember 2018, 14:03:29 CET schrieb agajjar:
>
> On 12/1/2018 3:38 PM, Oskari Lemmela wrote:
> > Rockpro64 is not able boot if kernel is compiled with
> > CONFIG_DRM_ROCKCHIP=m
> >
> > Enable Rockpro64 board HDMI output to fix issue.
>
> Hi Oskari,
>
> Could you please describe this issue in detail.
>
> I am not able to reproduce this issue if CONFIG_DRM_ROCKCHIP is compile
> in or as a loadable module at the same time hdmi node is present or not.
I've now simply adjusted the commit message to:
"arm64: dts: rockchip: enable hdmi output on rk3399-rockpro64
The rockpro64 does have hdmi support, so add the necessary
devicetree node to enable it."
and applied it for 4.21.
While it still would be good to find out where the issue comes from Oskari
is seeing, the rockpro64 does have hdmi, so we can just enable it ;-)
Heiko
prev parent reply other threads:[~2018-12-06 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 10:08 [PATCH 0/2] arm64: dts: rockchip: rockpro64 dts issues Oskari Lemmela
2018-12-01 10:08 ` [PATCH 1/2] arm64: dts: rockchip: rockpro64 fix regulator gpios Oskari Lemmela
2018-12-05 12:59 ` agajjar
2018-12-06 12:48 ` Heiko Stuebner
2018-12-01 10:08 ` [PATCH 2/2] arm64: dts: rockchip: rockpro64 fix video output chain Oskari Lemmela
2018-12-05 13:03 ` agajjar
2018-12-06 13:03 ` 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=3141294.pN5WgFrMoD@phil \
--to=heiko@sntech.de \
--cc=Akash_Gajjar@mentor.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=oskari@lemmela.net \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).