linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ivan T. Ivanov" <iivanov@suse.de>
To: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>
Cc: Maxime Ripard <maxime@cerno.tech>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Ivan T. Ivanov" <iivanov@suse.de>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>
Subject: [PATCH v2 2/2] clk: bcm: rpi: Handle pixel clock in firmware
Date: Tue,  5 Apr 2022 11:25:03 +0300	[thread overview]
Message-ID: <20220405082503.61041-3-iivanov@suse.de> (raw)
In-Reply-To: <20220405082503.61041-1-iivanov@suse.de>

The clk-bcm2835 handling of the pixel clock does not function
correctly when the HDMI power domain is disabled.

The firmware supports it correctly, so add it to the
firmware clock driver.

Cc: Dave Stevenson <dave.stevenson@raspberrypi.com>
Signed-off-by: Ivan T. Ivanov <iivanov@suse.de>
---
 drivers/clk/bcm/clk-raspberrypi.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/clk/bcm/clk-raspberrypi.c b/drivers/clk/bcm/clk-raspberrypi.c
index 2e2491d85835..530820d13104 100644
--- a/drivers/clk/bcm/clk-raspberrypi.c
+++ b/drivers/clk/bcm/clk-raspberrypi.c
@@ -129,6 +129,9 @@ raspberrypi_clk_variants[RPI_FIRMWARE_NUM_CLK_ID] = {
 	[RPI_FIRMWARE_V3D_CLK_ID] = {
 		.export = true,
 	},
+	[RPI_FIRMWARE_PIXEL_CLK_ID] = {
+		.export = true,
+	},
 	[RPI_FIRMWARE_HEVC_CLK_ID] = {
 		.export = true,
 	},
-- 
2.26.2


  parent reply	other threads:[~2022-04-05 10:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05  8:25 [PATCH v2 0/2] clk: bcm: rpi: Add support for two more clocks Ivan T. Ivanov
2022-04-05  8:25 ` [PATCH v2 1/2] clk: bcm: rpi: Add support HEVC clock Ivan T. Ivanov
2022-04-05  8:25 ` Ivan T. Ivanov [this message]
2022-04-05 11:21   ` [PATCH v2 2/2] clk: bcm: rpi: Handle pixel clock in firmware Dave Stevenson
2022-04-05  9:04 ` [PATCH v2 0/2] clk: bcm: rpi: Add support for two more clocks Maxime Ripard
2022-04-15  7:48   ` Ivan T. Ivanov
2022-04-15  8:38     ` Stefan Wahren

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=20220405082503.61041-3-iivanov@suse.de \
    --to=iivanov@suse.de \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime@cerno.tech \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@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).