From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Samsung SoC <linux-samsung-soc@vger.kernel.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Nishanth Menon <nm@ti.com>, Stephen Boyd <sboyd@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Dave Gerlach <d-gerlach@ti.com>, Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH 0/2] cpufreq/opp: rework regulator initialization
Date: Fri, 8 Feb 2019 15:58:35 +0530 [thread overview]
Message-ID: <20190208102835.fjxyeyp3kkdwar5d@vireshk-i7> (raw)
In-Reply-To: <CAJZ5v0jB7CDd9+gX+R3e+yrEsJty1E2MwuJGnuaJS0QeHeJ5rg@mail.gmail.com>
On 08-02-19, 11:18, Rafael J. Wysocki wrote:
> Obviously, all I2C transfers need to take place either before
> suspending the I2C controller or after resuming it.
Right. But all I am saying is that it is the responsibility of the
cpufreq core/driver to make sure we call ->init() only when the
resources are available to be used. For example during driver load, we
defer probe if resources aren't available and that makes sure ->init()
gets called when we can actually change the frequency.
Shouldn't the same be true during resume? That is make sure all
resources are in place before ->init() gets called ?
--
viresh
next prev parent reply other threads:[~2019-02-08 10:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190207122255eucas1p1cdebed838c799eca46cce6a654a26187@eucas1p1.samsung.com>
2019-02-07 12:22 ` [PATCH 0/2] cpufreq/opp: rework regulator initialization Marek Szyprowski
[not found] ` <CGME20190207122255eucas1p1444023f01217a43cfb958fe0bd48ef4d@eucas1p1.samsung.com>
2019-02-07 12:22 ` [PATCH 1/2] cpufreq: dt/ti/opp: move regulators initialization to the drivers Marek Szyprowski
[not found] ` <CGME20190207122256eucas1p17e8742176bda911263d2d14d2797a886@eucas1p1.samsung.com>
2019-02-07 12:22 ` [PATCH 2/2] cpufreq: dt: rework resources initialization Marek Szyprowski
2019-02-08 1:26 ` kbuild test robot
2019-02-08 1:26 ` kbuild test robot
2019-02-08 6:49 ` [PATCH 0/2] cpufreq/opp: rework regulator initialization Viresh Kumar
2019-02-08 8:12 ` Marek Szyprowski
2019-02-08 8:55 ` Viresh Kumar
2019-02-08 9:15 ` Marek Szyprowski
2019-02-08 9:23 ` Viresh Kumar
2019-02-08 10:02 ` Marek Szyprowski
2019-02-08 10:08 ` Rafael J. Wysocki
2019-02-08 10:18 ` Rafael J. Wysocki
2019-02-08 10:28 ` Viresh Kumar [this message]
2019-02-08 10:22 ` Rafael J. Wysocki
2019-02-08 10:31 ` Marek Szyprowski
2019-02-08 10:31 ` Viresh Kumar
2019-02-08 10:42 ` Rafael J. Wysocki
2019-02-08 10:52 ` Rafael J. Wysocki
2019-02-08 11:39 ` Sudeep Holla
2019-02-08 12:03 ` Rafael J. Wysocki
2019-02-08 12:09 ` Sudeep Holla
2019-02-08 12:23 ` Rafael J. Wysocki
2019-02-08 14:28 ` Sudeep Holla
2019-02-08 11:00 ` Sudeep Holla
2019-02-08 11:47 ` Marek Szyprowski
2019-02-08 11:51 ` Sudeep Holla
2019-02-08 12:04 ` Marek Szyprowski
2019-02-08 12:11 ` Rafael J. Wysocki
2019-02-08 12:16 ` Sudeep Holla
2019-02-08 17:41 ` Sudeep Holla
2019-02-11 8:47 ` Viresh Kumar
2019-02-11 14:08 ` Sudeep Holla
2019-02-11 8:44 ` Viresh Kumar
2019-02-11 9:52 ` Marek Szyprowski
2019-02-11 9:55 ` Viresh Kumar
2019-02-11 12:22 ` Marek Szyprowski
2019-02-12 5:08 ` Viresh Kumar
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=20190208102835.fjxyeyp3kkdwar5d@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=d-gerlach@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sboyd@kernel.org \
--cc=wsa@the-dreams.de \
/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.