From: Jerome Brunet <jbrunet@baylibre.com>
To: Neil Armstrong <neil.armstrong@linaro.org>
Cc: Kevin Hilman <khilman@baylibre.com>,
linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org,
devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH 0/2] arm64: dts: amlogic: handle hdmi system clock
Date: Fri, 28 Jun 2024 11:10:43 +0200 [thread overview]
Message-ID: <1j7ce9xwj0.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <16ec9c9a-badb-4626-9227-fb03f0ee3ee6@linaro.org> (Neil Armstrong's message of "Fri, 28 Jun 2024 10:10:22 +0200")
On Fri 28 Jun 2024 at 10:10, Neil Armstrong <neil.armstrong@linaro.org> wrote:
> Hi,
>
> On 26/06/2024 17:27, Jerome Brunet wrote:
>> This patchset adds the setup of the HDMI system clock for HDMI Tx.
>> This is another step in cleaning HDMI Tx and its direct usage of HHI
>> register space. Eventually, this will help remove component usage from
>> the Amlogic display drivers.
>
> Thanks,
>
> Beware we will need to keep old DT with new kernel functional for a while,
> do removal of component & HHI in meson_dw_hdmi would need to wait for multiple
> kernel releases.
Oh, I'm aware of the pain DT backward compatibility will be on this one.
Situation is slightly more complex than the PWM ...
I'm not sure how keeping support both for the 'legacy HHI direct access'
and 'modern API and region' approaches will look like. It's likely to be a
mess.
What I posted so far are things I'm sure of and will not cause issue.
When I get to the controversial stuff, I'll post an RFC first.
>
> A migration step would be to add a phandle to hhi right now, so we can drop
> components earlier, then in a second time add a proper PHY and then mark
> the hhi reg as deprecated.
Giving the hhi syscon to HDMI-Tx is solving half the problem.
IMO, HDMI-TX should just get the HDMI PHY register space in HHI. Indeed
that could be added now as well, without causing issue to the existing
DTs and drivers.
The display drivers should not directly poke in the HHI bus, nor should it have
access to the whole bus.
If we are going to take the pain of fixing the DT interface, better do
it once and for all.
The 2 main HHI offenders are HDMI-Tx and vclk:
* HDMI-TX: I've got the that mostly sorted out, for an RFC at least.
* Vclk: Here it is more a matter CCF usage that HHI
* The HDMI pll could use the regular DCO/mult-range driver from what I
can see
* The vclk display would need to get the DCO clock along with all the
ODs/divider handle. Without rate propagation, it would be free to
recreate the setups it needs. I don't have the full list and I did
not spend much time on this yet but that's the idea.
>
> Neil
>
>> Jerome Brunet (2):
>> arm64: dts: amlogic: gx: correct hdmi clocks
>> arm64: dts: amlogic: setup hdmi system clock
>> arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi | 5 +++++
>> arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 9 +++++++--
>> arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 9 +++++++--
>> 3 files changed, 19 insertions(+), 4 deletions(-)
>>
--
Jerome
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2024-06-28 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 15:27 Jerome Brunet
2024-06-26 15:27 ` [PATCH 1/2] arm64: dts: amlogic: gx: correct hdmi clocks Jerome Brunet
2024-06-26 15:27 ` [PATCH 2/2] arm64: dts: amlogic: setup hdmi system clock Jerome Brunet
2024-06-28 8:10 ` [PATCH 0/2] arm64: dts: amlogic: handle " Neil Armstrong
2024-06-28 9:10 ` Jerome Brunet [this message]
2024-06-28 8:12 ` Neil Armstrong
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=1j7ce9xwj0.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@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
all inboxes | Powered by JetHome®