From: Florian Fainelli <f.fainelli@gmail.com>
To: Maxime Ripard <maxime@cerno.tech>,
Stephen Boyd <sboyd@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Maxime Ripard <mripard@kernel.org>,
Scott Branden <sbranden@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Michael Turquette <mturquette@baylibre.com>,
Daniel Vetter <daniel@ffwll.ch>, Emma Anholt <emma@anholt.net>,
David Airlie <airlied@linux.ie>, Ray Jui <rjui@broadcom.com>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
dri-devel@lists.freedesktop.org,
Dom Cobley <popcornmix@gmail.com>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: Re: [PATCH v5 3/7] firmware: raspberrypi: Provide a helper to query a clock max rate
Date: Thu, 27 Oct 2022 09:17:51 -0700 [thread overview]
Message-ID: <5c26e62a-0e69-aad6-c72f-eb7fc28051cb@gmail.com> (raw)
In-Reply-To: <20220815-rpi-fix-4k-60-v5-3-fe9e7ac8b111@cerno.tech>
On 10/27/2022 5:52 AM, Maxime Ripard wrote:
> The firmware allows to query for its clocks the operating range of a
> given clock. We'll need this for some drivers (KMS, in particular) to
> infer the state of some configuration options, so let's create a
> function to do so.
>
> Acked-by: Stephen Boyd <sboyd@kernel.org>
> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
_______________________________________________
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-10-27 16:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 12:52 [PATCH v5 0/7] drm/vc4: Fix the core clock behaviour Maxime Ripard
2022-10-27 12:52 ` [PATCH v5 1/7] firmware: raspberrypi: Introduce rpi_firmware_find_node() Maxime Ripard
2022-10-27 12:52 ` [PATCH v5 2/7] firmware: raspberrypi: Move the clock IDs to the firmware header Maxime Ripard
2022-10-27 12:52 ` [PATCH v5 3/7] firmware: raspberrypi: Provide a helper to query a clock max rate Maxime Ripard
2022-10-27 16:17 ` Florian Fainelli [this message]
2022-10-27 12:52 ` [PATCH v5 4/7] drm/vc4: hdmi: Fix hdmi_enable_4kp60 detection Maxime Ripard
2022-10-27 12:52 ` [PATCH v5 5/7] drm/vc4: hdmi: Rework hdmi_enable_4kp60 detection code Maxime Ripard
2022-10-27 13:58 ` Dave Stevenson
2022-10-27 12:52 ` [PATCH v5 6/7] drm/vc4: hdmi: Add more checks for 4k resolutions Maxime Ripard
2022-10-27 12:52 ` [PATCH v5 7/7] drm/vc4: Make sure we don't end up with a core clock too high Maxime Ripard
2022-10-27 14:59 ` [PATCH v5 0/7] drm/vc4: Fix the core clock behaviour Maxime Ripard
2022-10-27 16:18 ` Florian Fainelli
2022-10-28 11:06 ` Maxime Ripard
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=5c26e62a-0e69-aad6-c72f-eb7fc28051cb@gmail.com \
--to=f.fainelli@gmail.com \
--cc=airlied@linux.ie \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=daniel@ffwll.ch \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emma@anholt.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=maxime@cerno.tech \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=popcornmix@gmail.com \
--cc=rjui@broadcom.com \
--cc=sboyd@kernel.org \
--cc=sbranden@broadcom.com \
--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).