[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKohpo=V_7a3-gDr0qoH=uPnH3+=SNGtgFWPzSU7U61uKqsHyg@mail.gmail.com>
Date: Wed, 23 May 2018 17:21:00 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Ilia Lin <ilialin@...eaurora.org>
Cc: Sudeep Holla <sudeep.holla@....com>,
Viresh Kumar <vireshk@...nel.org>, Nishanth Menon <nm@...com>,
Stephen Boyd <sboyd@...nel.org>, Rob Herring <robh@...nel.org>,
Mark Rutland <mark.rutland@....com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v10 1/2] cpufreq: Add Kryo CPU scaling driver
On 23 May 2018 at 17:17, <ilialin@...eaurora.org> wrote:
> The nvmem will return EPROBE_DEFER, and so will my driver's init. But then no one will call the init again.
So even your driver needs to be registered as a platform driver then
and you can create its device
from the init function, and add a comment on why you create the
platform device in the driver itself.
--
viresh
Powered by blists - more mailing lists