From: Viresh Kumar <viresh.kumar@linaro.org> To: k.konieczny@samsung.com, peron.clem@gmail.com, m.szyprowski@samsung.com, Nishanth Menon <nm@ti.com>, Stephen Boyd <sboyd@kernel.org>, Viresh Kumar <vireshk@kernel.org> Cc: Viresh Kumar <viresh.kumar@linaro.org>, linux-pm@vger.kernel.org, Vincent Guittot <vincent.guittot@linaro.org>, Rafael Wysocki <rjw@rjwysocki.net>, broonie@kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/2] opp: core: add regulators enable and disable Date: Fri, 15 May 2020 13:27:19 +0530 Message-ID: <cover.1589528491.git.viresh.kumar@linaro.org> (raw) Hi, This series reintroduces the usage of regulator_enable/disable() to the OPP core after the previous attempt was reverted [1] shortly after getting applied. This time the regulator is enabled only after it is configured by the OPP core. Marek, Kamil and Clément: Can you guys please test this out and report if this doesn't work as expected ? -- viresh [1] https://lore.kernel.org/lkml/20191017102758.8104-1-m.szyprowski@samsung.com/ Kamil Konieczny (1): opp: core: add regulators enable and disable Viresh Kumar (1): opp: Reorder the code for !target_freq case drivers/opp/core.c | 39 ++++++++++++++++++++++++++++++++++----- drivers/opp/opp.h | 2 ++ 2 files changed, 36 insertions(+), 5 deletions(-) -- 2.25.0.rc1.19.g042ed3e048af
next reply index Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CGME20200515075745eucas1p2f14c7fcec7c3d190704ddc6f608b6ce9@eucas1p2.samsung.com> 2020-05-15 7:57 ` Viresh Kumar [this message] 2020-05-15 7:57 ` [PATCH 1/2] opp: Reorder the code for !target_freq case Viresh Kumar 2020-05-15 7:57 ` [PATCH 2/2] opp: core: add regulators enable and disable Viresh Kumar 2020-05-15 9:16 ` [PATCH 0/2] " Marek Szyprowski 2020-05-15 12:00 ` Clément Péron 2020-05-21 12:23 ` Clément Péron
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=cover.1589528491.git.viresh.kumar@linaro.org \ --to=viresh.kumar@linaro.org \ --cc=broonie@kernel.org \ --cc=k.konieczny@samsung.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=m.szyprowski@samsung.com \ --cc=nm@ti.com \ --cc=peron.clem@gmail.com \ --cc=rjw@rjwysocki.net \ --cc=sboyd@kernel.org \ --cc=vincent.guittot@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
Linux-PM Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-pm/0 linux-pm/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-pm linux-pm/ https://lore.kernel.org/linux-pm \ linux-pm@vger.kernel.org public-inbox-index linux-pm Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-pm AGPL code for this site: git clone https://public-inbox.org/public-inbox.git