From: Dmitry Osipenko <digetx@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 3/3] opp: Add dev_pm_opp_of_add_table_noclk()
Date: Tue, 2 Feb 2021 21:04:04 +0300 [thread overview]
Message-ID: <5130bbcf-2531-a5d4-4f30-315bbf485711@gmail.com> (raw)
In-Reply-To: <20210202050230.g7xxo6373stfvzbi@vireshk-i7>
02.02.2021 08:02, Viresh Kumar пишет:
> On 01-02-21, 23:00, Dmitry Osipenko wrote:
>> 28.01.2021 10:00, Viresh Kumar пишет:
>>> A few drivers have device's clk but they don't want the OPP core to
>>> handle that. Add a new helper for them, dev_pm_opp_of_add_table_noclk().
>>>
>>> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>>> ---
>>> V2:
>>> - Split this into a separate patch.
>>>
>>> drivers/opp/of.c | 18 ++++++++++++++++++
>>> include/linux/pm_opp.h | 6 ++++++
>>> 2 files changed, 24 insertions(+)
>>
>> For the all current/latest OPP patches:
>>
>> Tested-by: Dmitry Osipenko <digetx@gmail.com>
>
> Hmm, I have now added your Tested-by to all the patches that we worked
> together on..
>
> Thanks.
>
That's exactly what I meant, thank you.
prev parent reply other threads:[~2021-02-02 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 7:00 [PATCH V2 1/3] opp: Create _of_add_table_indexed() to reduce code duplication Viresh Kumar
2021-01-28 7:00 ` [PATCH V2 2/3] opp: Defer acquiring the clk until OPPs are added Viresh Kumar
2021-01-28 7:00 ` [PATCH V2 3/3] opp: Add dev_pm_opp_of_add_table_noclk() Viresh Kumar
2021-02-01 20:00 ` Dmitry Osipenko
2021-02-02 5:02 ` Viresh Kumar
2021-02-02 18:04 ` Dmitry Osipenko [this message]
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=5130bbcf-2531-a5d4-4f30-315bbf485711@gmail.com \
--to=digetx@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@kernel.org \
--cc=vincent.guittot@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®