[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87muiwzyrw.fsf@anholt.net>
Date: Tue, 04 Jun 2019 17:00:51 -0700
From: Eric Anholt <eric@...olt.net>
To: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>,
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,
Nicolas Saenz Julienne <nsaenzjulienne@...e.de>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/4] clk: bcm2835: register Raspberry Pi's firmware clk device
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).
Download attachment "signature.asc" of type "application/pgp-signature" (833 bytes)
Powered by blists - more mailing lists