Re: [PATCH 07/89] clk: bcm: rpi: Allow the driver to be probed by DT

Hi Stefan, On Sun, Mar 01, 2020 at 01:16:28PM +0100, Stefan Wahren wrote: > Hi Maxime, > > Am 24.02.20 um 10:06 schrieb Maxime Ripard: > > The current firmware clock driver for the RaspberryPi can only be probed by > > manually registering an associated platform_device. > > > > While this works fi

Re: [PATCH 07/89] clk: bcm: rpi: Allow the driver to be probed by DT

Hi Maxime, Am 24.02.20 um 10:06 schrieb Maxime Ripard: > The current firmware clock driver for the RaspberryPi can only be probed by > manually registering an associated platform_device. > > While this works fine for cpufreq where the device gets attached a clkdev > lookup, it would be tedious to

Re: [PATCH 07/89] clk: bcm: rpi: Allow the driver to be probed by DT

Hi Maxime, On Wed, 2020-02-26 at 16:01 +0100, Maxime Ripard wrote: [...] > This was actually a shameless bait to start that discussion, so I'm > glad it worked ;) :) [...] > > - Some of those fw managed clocks you're creating have their mmio > > counterpart > > being registered by clk-bcm23

Re: [PATCH 07/89] clk: bcm: rpi: Allow the driver to be probed by DT

Hi Nicolas, On Tue, Feb 25, 2020 at 05:00:56PM +0100, Nicolas Saenz Julienne wrote: > On Mon, 2020-02-24 at 10:06 +0100, Maxime Ripard wrote: > > The current firmware clock driver for the RaspberryPi can only be probed by > > manually registering an associated platform_device. > > > > While this w

Re: [PATCH 07/89] clk: bcm: rpi: Allow the driver to be probed by DT

Hi Maxime, On Mon, 2020-02-24 at 10:06 +0100, Maxime Ripard wrote: > The current firmware clock driver for the RaspberryPi can only be probed by > manually registering an associated platform_device. > > While this works fine for cpufreq where the device gets attached a clkdev > lookup, it would b