From: Justin Swartz <justin.swartz@risingedge.co.za>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: rockchip: add display nodes for rk322x
Date: Fri, 14 Jun 2019 18:22:55 +0200 [thread overview]
Message-ID: <9e2b1e26bedfd30e9295d64865819c99@risingedge.co.za> (raw)
In-Reply-To: <1854794.0zkvb3x0FP@phil>
Hi Heiko,
On 2019-06-14 11:15, Heiko Stuebner wrote:
> Hi Justin,
>
> Am Donnerstag, 13. Juni 2019, 12:13:04 CEST schrieb Justin Swartz:
>
>> Add display_subsystem, hdmi_phy, vop, and hdmi device nodes plus
>> a few hdmi pinctrl entries to allow for HDMI output.
>>
>> Signed-off-by: Justin Swartz <justin.swartz@risingedge.co.za>
>
> Overall looks good, but in combination with the clock-patch you posted,
> I'd really prefer if we could try a slightly different approach.
>
> Hard register-level settings in the clock driver look bad and tend to
> cause problems later on, so I've adapted things a bit in [0] (untested)
> and would be glad if you could give it a try on actual hardware.
I can confirm that your approach works properly here.
> The hdmiphy itself is a clock-provider for its pll and therefore the
> assigned-clock* properties into the hdmi controller, as the phy needs
> to probe before trying to set clocks.
> But in theory this should achieve the same result of reparenting the
> system's hdmiphy clock to the actual output of the phy-pll.
>
> I've also moved the iommu-cells fix to a separate commit.
>
> Please test, thanks
> Heiko
>
> [0] https://github.com/mmind/linux-rockchip/commits/wip/rk3229-hdmi
Thanks
Justin
next prev parent reply other threads:[~2019-06-14 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 10:13 [PATCH] ARM: dts: rockchip: add display nodes for rk322x Justin Swartz
2019-06-14 9:15 ` Heiko Stuebner
2019-06-14 16:22 ` Justin Swartz [this message]
2019-06-21 15:51 ` Johan Jonker
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=9e2b1e26bedfd30e9295d64865819c99@risingedge.co.za \
--to=justin.swartz@risingedge.co.za \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--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=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