linux-kernel - Re: [PATCH] ARM64: dts: meson-gx: Use correct mmc clock source 0

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:   Tue, 01 Aug 2017 12:48:48 -0700
From:   Kevin Hilman <khilman@...libre.com>
To:     Jerome Brunet <jbrunet@...libre.com>
Cc:     Carlo Caione <carlo@...one.org>, devicetree@...r.kernel.org,
        linux-amlogic@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARM64: dts: meson-gx: Use correct mmc clock source 0

Jerome Brunet <jbrunet@...libre.com> writes:

> Now that the clock source 0 is properly described in the CCF, use it
> instead of assuming the default value (xtal)
>
> Signed-off-by: Jerome Brunet <jbrunet@...libre.com>
> ---
>
> This patchset depends on clock patchset adding the related clocks:
> * https://lkml.kernel.org/r/20170731115603.29720-1-jbrunet@baylibre.com

I'll need a stable tag/commit in clk-meson/next/drivers to use in order
to apply this one.

Kevin