[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <17ea99902e4329db735080d1a8fc04f5c06c9bf0.camel@suse.de>
Date: Wed, 05 Jun 2019 11:11:12 +0200
From: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
To: Eric Anholt <eric@...olt.net>, stefan.wahren@...e.com,
Florian Fainelli <f.fainelli@...il.com>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
bcm-kernel-feedback-list@...adcom.com
Cc: mbrugger@...e.de, viresh.kumar@...aro.org, rjw@...ysocki.net,
sboyd@...nel.org, 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,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/4] clk: bcm2835: register Raspberry Pi's firmware clk
device
On Tue, 2019-06-04 at 17:00 -0700, Eric Anholt wrote:
> Nicolas Saenz Julienne <nsaenzjulienne@...e.de> writes:
>
> > Registers clk-raspberrypi as a platform device as part of the driver's
> > probe sequence.
>
> Similar to how we have VCHI register platform devices for the services
> VCHI provides, shouldn't we have the firmware driver register the device
> for clk_raspberrypi? Or put the clk provider in the fw driver instead
> of a separate driver (no opinion on my part).
Makes sense to me, I'll move the platform driver registration into the firmware
driver.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists