All of lore.kernel.org
 help / color / mirror / Atom feed
From: <ilialin@codeaurora.org>
To: "'Viresh Kumar'" <viresh.kumar@linaro.org>
Cc: "'Sudeep Holla'" <sudeep.holla@arm.com>,
	"'Viresh Kumar'" <vireshk@kernel.org>,
	"'Nishanth Menon'" <nm@ti.com>,
	"'Stephen Boyd'" <sboyd@kernel.org>,
	"'Rob Herring'" <robh@kernel.org>,
	"'Mark Rutland'" <mark.rutland@arm.com>,
	"'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
	<linux-pm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v10 1/2] cpufreq: Add Kryo CPU scaling driver
Date: Wed, 23 May 2018 14:47:24 +0300	[thread overview]
Message-ID: <002d01d3f28b$d3ce3980$7b6aac80$@codeaurora.org> (raw)
In-Reply-To: <CAKohponruWpcjuSDg-=ZbZ1=qm2iPZs36mfKYJ3nQZREkc3JCw@mail.gmail.com>

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@linaro.org>
> Sent: Wednesday, May 23, 2018 14:46
> To: Ilia Lin <ilialin@codeaurora.org>
> Cc: Sudeep Holla <sudeep.holla@arm.com>; Viresh Kumar
> <vireshk@kernel.org>; Nishanth Menon <nm@ti.com>; Stephen Boyd
> <sboyd@kernel.org>; Rob Herring <robh@kernel.org>; Mark Rutland
> <mark.rutland@arm.com>; Rafael J. Wysocki <rjw@rjwysocki.net>; linux-
> pm@vger.kernel.org; devicetree@vger.kernel.org; Linux Kernel Mailing List
> <linux-kernel@vger.kernel.org>
> Subject: Re: [PATCH v10 1/2] cpufreq: Add Kryo CPU scaling driver
> 
> On 23 May 2018 at 17:04,  <ilialin@codeaurora.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 ?

WARNING: multiple messages have this Message-ID (diff)
From: <ilialin@codeaurora.org>
To: 'Viresh Kumar' <viresh.kumar@linaro.org>
Cc: 'Sudeep Holla' <sudeep.holla@arm.com>,
	'Viresh Kumar' <vireshk@kernel.org>, 'Nishanth Menon' <nm@ti.com>,
	'Stephen Boyd' <sboyd@kernel.org>,
	'Rob Herring' <robh@kernel.org>,
	'Mark Rutland' <mark.rutland@arm.com>,
	"'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	'Linux Kernel Mailing List' <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v10 1/2] cpufreq: Add Kryo CPU scaling driver
Date: Wed, 23 May 2018 14:47:24 +0300	[thread overview]
Message-ID: <002d01d3f28b$d3ce3980$7b6aac80$@codeaurora.org> (raw)
In-Reply-To: <CAKohponruWpcjuSDg-=ZbZ1=qm2iPZs36mfKYJ3nQZREkc3JCw@mail.gmail.com>

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@linaro.org>
> Sent: Wednesday, May 23, 2018 14:46
> To: Ilia Lin <ilialin@codeaurora.org>
> Cc: Sudeep Holla <sudeep.holla@arm.com>; Viresh Kumar
> <vireshk@kernel.org>; Nishanth Menon <nm@ti.com>; Stephen Boyd
> <sboyd@kernel.org>; Rob Herring <robh@kernel.org>; Mark Rutland
> <mark.rutland@arm.com>; Rafael J. Wysocki <rjw@rjwysocki.net>; linux-
> pm@vger.kernel.org; devicetree@vger.kernel.org; Linux Kernel Mailing List
> <linux-kernel@vger.kernel.org>
> Subject: Re: [PATCH v10 1/2] cpufreq: Add Kryo CPU scaling driver
> 
> On 23 May 2018 at 17:04,  <ilialin@codeaurora.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 ?

  reply	other threads:[~2018-05-23 11:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23  9:40 [PATCH v10 0/2] Kryo CPU scaling driver Ilia Lin
2018-05-23  9:40 ` [PATCH v10 1/2] cpufreq: Add " Ilia Lin
2018-05-23 10:03   ` Viresh Kumar
2018-05-23 10:39   ` Sudeep Holla
2018-05-23 11:06     ` ilialin
2018-05-23 11:06       ` ilialin
2018-05-23 11:31       ` Viresh Kumar
2018-05-23 11:34         ` ilialin
2018-05-23 11:34           ` ilialin
2018-05-23 11:46           ` Viresh Kumar
2018-05-23 11:47             ` ilialin [this message]
2018-05-23 11:47               ` ilialin
2018-05-23 11:51               ` Viresh Kumar
2018-05-23  9:40 ` [PATCH v10 2/2] dt-bindings: cpufreq: Document operating-points-v2-kryo-cpu Ilia Lin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002d01d3f28b$d3ce3980$7b6aac80$@codeaurora.org' \
    --to=ilialin@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=nm@ti.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=viresh.kumar@linaro.org \
    --cc=vireshk@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.