linux-kernel - RE: [PATCH v10 1/2] cpufreq: Add Kryo CPU scaling driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <002d01d3f28b$d3ce3980$7b6aac80$@codeaurora.org>
Date:   Wed, 23 May 2018 14:47:24 +0300
From:   <ilialin@...eaurora.org>
To:     "'Viresh Kumar'" <viresh.kumar@...aro.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>, <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

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 <viresh.kumar@...aro.org>
> Sent: Wednesday, May 23, 2018 14:46
> 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; 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:04,  <ilialin@...eaurora.org> wrote:
> > You are right. I already checked that in the code...
> > However, with module_init() the driver fails on reading the nvmem.
> 
> And why is it failing ?