From mboxrd@z Thu Jan 1 00:00:00 1970 From: Subject: RE: [PATCH v10 1/2] cpufreq: Add Kryo CPU scaling driver Date: Wed, 23 May 2018 14:47:24 +0300 Message-ID: <002d01d3f28b$d3ce3980$7b6aac80$@codeaurora.org> References: <1527068454-28921-1-git-send-email-ilialin@codeaurora.org> <1527068454-28921-2-git-send-email-ilialin@codeaurora.org> <3f1ca60e-7aa8-fccc-ab1c-4b7c37731cce@arm.com> <002901d3f286$198878b0$4c996a10$@codeaurora.org> <002b01d3f28a$0d033900$2709ab00$@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Language: en-us Sender: linux-kernel-owner@vger.kernel.org To: 'Viresh Kumar' Cc: 'Sudeep Holla' , 'Viresh Kumar' , 'Nishanth Menon' , 'Stephen Boyd' , 'Rob Herring' , 'Mark Rutland' , "'Rafael J. Wysocki'" , linux-pm@vger.kernel.org, devicetree@vger.kernel.org, 'Linux Kernel Mailing List' List-Id: devicetree@vger.kernel.org The nvmem will return EPROBE_DEFER, and so will my driver's init. But = then no one will call the init again. > -----Original Message----- > From: Viresh Kumar > Sent: Wednesday, May 23, 2018 14:46 > To: Ilia Lin > Cc: Sudeep Holla ; Viresh Kumar > ; Nishanth Menon ; Stephen Boyd > ; Rob Herring ; Mark Rutland > ; Rafael J. Wysocki ; linux- > pm@vger.kernel.org; devicetree@vger.kernel.org; Linux Kernel Mailing = List > > Subject: Re: [PATCH v10 1/2] cpufreq: Add Kryo CPU scaling driver >=20 > On 23 May 2018 at 17:04, wrote: > > You are right. I already checked that in the code... > > However, with module_init() the driver fails on reading the nvmem. >=20 > And why is it failing ?