linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: linux-amlogic@lists.infradead.org, jbrunet@baylibre.com,
	narmstrong@baylibre.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: [PATCH 0/2] clk: meson8b: allow the HDMI driver to manage "hdmi_sys"
Date: Tue, 31 Mar 2020 01:45:33 +0200	[thread overview]
Message-ID: <20200330234535.3327513-1-martin.blumenstingl@googlemail.com> (raw)

The "hdmi_sys" clock is driving the HDMI TX controller. The
controller's IP seems to use this clock for example to derived the DDC
clock.

Testing has shown that we can disable this clock without locking up the
system (as long as we don't read the HDMI TX registers while this clock
is disabled - this can't happen as we don't have a driver yet and once
we have one that driver will enable this clock).


Martin Blumenstingl (2):
  clk: meson8b: export the HDMI system clock
  clk: meson: meson8b: make the hdmi_sys clock tree mutable

 drivers/clk/meson/meson8b.c              | 6 +++---
 drivers/clk/meson/meson8b.h              | 1 -
 include/dt-bindings/clock/meson8b-clkc.h | 1 +
 3 files changed, 4 insertions(+), 4 deletions(-)

-- 
2.26.0


             reply	other threads:[~2020-03-30 23:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30 23:45 Martin Blumenstingl [this message]
2020-03-30 23:45 ` [PATCH 1/2] clk: meson8b: export the HDMI system clock Martin Blumenstingl
2020-04-10 17:46   ` Rob Herring
2020-03-30 23:45 ` [PATCH 2/2] clk: meson: meson8b: make the hdmi_sys clock tree mutable Martin Blumenstingl
2020-04-14 13:01 ` [PATCH 0/2] clk: meson8b: allow the HDMI driver to manage "hdmi_sys" Jerome Brunet

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=20200330234535.3327513-1-martin.blumenstingl@googlemail.com \
    --to=martin.blumenstingl@googlemail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=narmstrong@baylibre.com \
    /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).