linux-kernel - Re: [PATCH 2/2] ARM: dts: bcm2835-rpi: Use firmware clocks for display

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20221109182415.879238-1-f.fainelli@gmail.com>
Date:   Wed,  9 Nov 2022 10:24:15 -0800
From:   Florian Fainelli <f.fainelli@...il.com>
To:     bcm-kernel-feedback-list@...adcom.com, maxime@...no.tech,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Ray Jui <rjui@...adcom.com>,
        Scott Branden <sbranden@...adcom.com>
Cc:     linux-rpi-kernel@...ts.infradead.org,
        Dave Stevenson <dave.stevenson@...pberrypi.com>,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        Phil Elwell <phil@...pberrypi.com>,
        linux-kernel@...r.kernel.org, Dom Cobley <dom@...pberrypi.com>
Subject: Re: [PATCH 2/2] ARM: dts: bcm2835-rpi: Use firmware clocks for display

On Wed, 26 Oct 2022 15:17:39 +0200, maxime@...no.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@...no.tech>
> ---

Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!
--
Florian