linux-kernel - Re: [PATCH 1/5] clk: inherit clocks enabled by bootloader

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]

Date:   Mon, 01 Jul 2019 11:25:36 -0700
From:   Eric Anholt <eric@...olt.net>
To:     Rob Clark <robdclark@...il.com>, dri-devel@...ts.freedesktop.org,
        linux-arm-msm@...r.kernel.org
Cc:     Rob Clark <robdclark@...omium.org>,
        aarch64-laptops@...ts.linaro.org, linux-pm@...r.kernel.org,
        Stephen Boyd <sboyd@...nel.org>,
        Michael Turquette <mturquette@...libre.com>,
        linux-kernel@...r.kernel.org, Andy Gross <agross@...nel.org>,
        freedreno@...ts.freedesktop.org, linux-clk@...r.kernel.org
Subject: Re: [PATCH 1/5] clk: inherit clocks enabled by bootloader

Rob Clark <robdclark@...il.com> writes:

> From: Rob Clark <robdclark@...omium.org>
>
> The goal here is to support inheriting a display setup by bootloader,
> although there may also be some non-display related use-cases.
>
> Rough idea is to add a flag for clks and power domains that might
> already be enabled when kernel starts, and which should not be
> disabled at late_initcall if the kernel thinks they are "unused".
>
> If bootloader is enabling display, and kernel is using efifb before
> real display driver is loaded (potentially from kernel module after
> userspace starts, in a typical distro kernel), we don't want to kill
> the clocks and power domains that are used by the display before
> userspace starts.
>
> Signed-off-by: Rob Clark <robdclark@...omium.org>

Raspberry Pi is carrying downstream hacks to do similar stuff, and it
would be great to see CCF finally support this.

Download attachment "signature.asc" of type "application/pgp-signature" (833 bytes)