From: Kever Yang <kever.yang@rock-chips.com>
To: Jagan Teki <jagan@amarulasolutions.com>,
Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>,
Anatolij Gustschin <agust@denx.de>,
Suniel Mahesh <sunil@amarulasolutions.com>,
U-Boot-Denx <u-boot@lists.denx.de>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
linux-amarula <linux-amarula@amarulasolutions.com>
Subject: Re: [PATCH v2 1/4] arm64: dts: rk3399-u-boot: Delete vop assigned-clocks/rates
Date: Thu, 2 Apr 2020 17:18:03 +0800 [thread overview]
Message-ID: <103f3c97-e223-6718-bb08-0aa2395145a2@rock-chips.com> (raw)
In-Reply-To: <CAMty3ZCHTk5H60cNmUhfq=pNwBJ9Kc1KuGGb=gQFCp2SS3_1gw@mail.gmail.com>
Hi Jagan,
On 2020/3/31 下午1:59, Jagan Teki wrote:
> On Tue, Mar 31, 2020 at 1:06 AM Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
>>> From: Jagan Teki <jagan@amarulasolutions.com>
>>> Cc: sunil@amarulasolutions.com, u-boot@lists.denx.de,
>>> linux-rockchip@lists.infradead.org, linux-amarula@amarulasolutions.com,
>>> Jagan Teki <jagan@amarulasolutions.com>
>>> Date: Mon, 30 Mar 2020 23:46:10 +0530
>>> Content-Type: text/plain; charset=UTF-8
>>>
>>> Linux supporting assigned-clocks for VOP on rk3399 by assuming
>>> U-Boot not initializing it on this linux commit:
>>>
>>> commit <617f4472bdd3> ("arm64: dts: rockchip: init rk3399 vop clock rates")
>>>
>>> There is no specific need to initialize these assigned clock
>>> in U-Boot as video drivers still work with default aclk and
>>> hclk values. So, these clocks are simply not supported by rk3399
>>> clock driver.
>>>
>>> But, during stdio probe of vidconsole, the device probe
>>> will try to check whether the assigned clocks on that video
>>> console node is initialized or not? and return error if not.
>>>
>>> So, delete these property via -u-boot dtsi as there is
>>> no specific need in U-Boot.
>> Deleting these properties isn't very helpful as it means the U-Boot
>> device tree can no longer be used by the kernel. Isn't it a better
>> idea to implement these clocks as stubs in the u-boot clock driver?
> I did try this before sorting out these changes, seems like it
> requires a bit more tweaking the clock wrt display code. I really
> didn't see any use case as of now for just to print u-boot log on
> display out, and more over this support has been broken since from
> releases. so bypassing these nodes can be a solutions for now.
I agree with Mark for not touch the dts first. I don't know the detail
of display driver but:
- The rk3399 driver use to work without touch dts from kernel;
- the clock driver have a rk3399_vop_set_clk() which does not depends on
dts.
Thanks,
- Kever
>
> Jagan.
>
>
next prev parent reply other threads:[~2020-04-02 9:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 18:16 [PATCH v2 0/4] rockchip: rk3399: Fix HDMI out Jagan Teki
[not found] ` <20200330181613.29462-1-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2020-03-30 18:16 ` [PATCH v2 1/4] arm64: dts: rk3399-u-boot: Delete vop assigned-clocks/rates Jagan Teki
2020-03-30 19:36 ` Mark Kettenis
[not found] ` <016151d6786a0ea4-Sse5TxTiDWuxJFhkpKByzTXZidJgq2Oi@public.gmane.org>
2020-03-31 5:59 ` Jagan Teki
2020-04-02 9:18 ` Kever Yang [this message]
2020-04-02 9:37 ` Jagan Teki
2020-04-02 10:18 ` Mark Kettenis
2020-04-02 11:42 ` Jagan Teki
2020-03-30 18:16 ` [PATCH v2 2/4] video: rockchip: Fix vop modes for rk3399 Jagan Teki
2020-03-30 18:16 ` [PATCH v2 3/4] rockchip: Enable pre console " Jagan Teki
2020-03-30 18:16 ` [PATCH v2 4/4] rockchip: Enable HDMI output on rk3399 board w/ HDMI Jagan Teki
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=103f3c97-e223-6718-bb08-0aa2395145a2@rock-chips.com \
--to=kever.yang@rock-chips.com \
--cc=agust@denx.de \
--cc=jagan@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.kettenis@xs4all.nl \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=sjg@chromium.org \
--cc=sunil@amarulasolutions.com \
--cc=u-boot@lists.denx.de \
/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