From: Stephen Boyd <sboyd@kernel.org>
To: Ivan T. Ivanov <iivanov@suse.de>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
bcm-kernel-feedback-list@broadcom.com, linux-clk@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Guillaume Gardet <Guillaume.Gardet@arm.com>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Ivan T. Ivanov <iivanov@suse.de>,
Maxime Ripard <maxime@cerno.tech>
Subject: Re: [RESEND v4 2/3] clk: bcm: rpi: Handle pixel clock in firmware
Date: Fri, 30 Sep 2022 14:34:56 -0700 [thread overview]
Message-ID: <20220930213459.56BF8C433D7@smtp.kernel.org> (raw)
In-Reply-To: <20220829152154.147250-3-iivanov@suse.de>
Quoting Ivan T. Ivanov (2022-08-29 08:21:53)
> 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.
>
> Acked-by: Maxime Ripard <maxime@cerno.tech>
> Acked-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
> Signed-off-by: Ivan T. Ivanov <iivanov@suse.de>
> ---
Applied to clk-next
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-30 21:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 15:21 [RESEND v4 0/3] clk: bcm: rpi: Add support for three more clocks Ivan T. Ivanov
2022-08-29 15:21 ` [RESEND v4 1/3] clk: bcm: rpi: Add support HEVC clock Ivan T. Ivanov
2022-09-30 21:34 ` Stephen Boyd
2022-08-29 15:21 ` [RESEND v4 2/3] clk: bcm: rpi: Handle pixel clock in firmware Ivan T. Ivanov
2022-09-30 21:34 ` Stephen Boyd [this message]
2022-08-29 15:21 ` [RESEND v4 3/3] clk: bcm: rpi: Add support for VEC clock Ivan T. Ivanov
2022-09-30 21:35 ` Stephen Boyd
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=20220930213459.56BF8C433D7@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=Guillaume.Gardet@arm.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=iivanov@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=maxime@cerno.tech \
--cc=nsaenz@kernel.org \
--cc=stefan.wahren@i2se.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).