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@xxxxxxxxxx> > Sent: Wednesday, May 23, 2018 14:46 > To: Ilia Lin <ilialin@xxxxxxxxxxxxxx> > Cc: Sudeep Holla <sudeep.holla@xxxxxxx>; Viresh Kumar > <vireshk@xxxxxxxxxx>; Nishanth Menon <nm@xxxxxx>; Stephen Boyd > <sboyd@xxxxxxxxxx>; Rob Herring <robh@xxxxxxxxxx>; Mark Rutland > <mark.rutland@xxxxxxx>; Rafael J. Wysocki <rjw@xxxxxxxxxxxxx>; linux- > pm@xxxxxxxxxxxxxxx; devicetree@xxxxxxxxxxxxxxx; Linux Kernel Mailing List > <linux-kernel@xxxxxxxxxxxxxxx> > Subject: Re: [PATCH v10 1/2] cpufreq: Add Kryo CPU scaling driver > > On 23 May 2018 at 17:04, <ilialin@xxxxxxxxxxxxxx> 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 ? -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
