From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com, maxime@cerno.tech,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: linux-rpi-kernel@lists.infradead.org,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Phil Elwell <phil@raspberrypi.com>,
linux-kernel@vger.kernel.org, Dom Cobley <dom@raspberrypi.com>
Subject: Re: [PATCH 2/2] ARM: dts: bcm2835-rpi: Use firmware clocks for display
Date: Wed, 9 Nov 2022 10:24:15 -0800 [thread overview]
Message-ID: <20221109182415.879238-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20221026-rpi-display-fw-clk-v1-2-5c29b7a3d8b0@cerno.tech>
On Wed, 26 Oct 2022 15:17:39 +0200, maxime@cerno.tech wrote:
> We've experienced a number of issues around the cohabitation between the
> "real" clock driver in Linux and the one backed by the firmware.
>
> One solution around this is to follow what the RaspberryPi foundation
> in its downstream clock, which is also what we've been doing on the
> RaspberryPi4: to use the clocks exposed by the firmware.
>
> Link: https://lore.kernel.org/linux-clk/20221021140505.kjmw5x4s6qhnrfif@houat/
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
> ---
Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!
--
Florian
next prev parent reply other threads:[~2022-11-09 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 13:17 [PATCH 0/2] ARM: dts: bcm283x: Switch to firmware clocks for Pi0-3 maxime
2022-10-26 13:17 ` [PATCH 1/2] ARM: dts: bcm283x: Remove bcm2835-rpi-common.dtsi from SoC DTSI maxime
2022-11-09 18:24 ` Florian Fainelli
2022-10-26 13:17 ` [PATCH 2/2] ARM: dts: bcm2835-rpi: Use firmware clocks for display maxime
2022-11-09 18:24 ` Florian Fainelli [this message]
2022-11-10 18:16 ` [PATCH 0/2] ARM: dts: bcm283x: Switch to firmware clocks for Pi0-3 Florian Fainelli
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=20221109182415.879238-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=devicetree@vger.kernel.org \
--cc=dom@raspberrypi.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=maxime@cerno.tech \
--cc=phil@raspberrypi.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.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
all inboxes | Powered by JetHome®