[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190625230505.9AFA72086D@mail.kernel.org>
Date: Tue, 25 Jun 2019 16:05:04 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>,
linux-kernel@...r.kernel.org, stefan.wahren@...e.com
Cc: mbrugger@...e.de, viresh.kumar@...aro.org, rjw@...ysocki.net,
eric@...olt.net, f.fainelli@...il.com,
bcm-kernel-feedback-list@...adcom.com, ptesarik@...e.com,
linux-rpi-kernel@...ts.infradead.org, ssuloev@...altech.com,
linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
mturquette@...libre.com, linux-pm@...r.kernel.org,
Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
Subject: Re: [PATCH v4 5/7] clk: raspberrypi: register platform device for raspberrypi-cpufreq
Quoting Nicolas Saenz Julienne (2019-06-12 11:24:57)
> As 'clk-raspberrypi' depends on RPi's firmware interface, which might be
> configured as a module, the cpu clock might not be available for the
> cpufreq driver during it's init process. So we register the
> 'raspberrypi-cpufreq' platform device after the probe sequence succeeds.
>
> Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
> Acked-by: Eric Anholt <eric@...olt.net>
> ---
Applied to clk-next
Powered by blists - more mailing lists