From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
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" <rafael@kernel.org>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] OPP: Add dev_pm_opp_find_freq_exact_indexed()
Date: Mon, 24 Jul 2023 11:54:05 +0530 [thread overview]
Message-ID: <20230724062405.GJ2370@thinkpad> (raw)
In-Reply-To: <852a47c0e7a795bdf6424519ab7fadfdeb5b4a3c.1689932341.git.viresh.kumar@linaro.org>
On Fri, Jul 21, 2023 at 03:10:57PM +0530, Viresh Kumar wrote:
> The indexed version of the API is added for other floor and ceil, add
> the same for exact as well for completeness.
>
Well, "completeness" makes sense to me but I always heard that you should add
an API when there is a user. That was the reason I didn't add it in my patch.
- Mani
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> drivers/opp/core.c | 28 ++++++++++++++++++++++++++++
> include/linux/pm_opp.h | 11 +++++++++++
> 2 files changed, 39 insertions(+)
>
> diff --git a/drivers/opp/core.c b/drivers/opp/core.c
> index 00638d40353f..7b1d5724b3d8 100644
> --- a/drivers/opp/core.c
> +++ b/drivers/opp/core.c
> @@ -648,6 +648,34 @@ struct dev_pm_opp *dev_pm_opp_find_freq_exact(struct device *dev,
> }
> EXPORT_SYMBOL_GPL(dev_pm_opp_find_freq_exact);
>
> +/**
> + * dev_pm_opp_find_freq_exact_indexed() - Search for an exact freq for the
> + * clock corresponding to the index
> + * @dev: Device for which we do this operation
> + * @freq: frequency to search for
> + * @index: Clock index
> + * @available: true/false - match for available opp
> + *
> + * Search for the matching exact OPP for the clock corresponding to the
> + * specified index from a starting freq for a device.
> + *
> + * Return: matching *opp , else returns ERR_PTR in case of error and should be
> + * handled using IS_ERR. Error return values can be:
> + * EINVAL: for bad pointer
> + * ERANGE: no match found for search
> + * ENODEV: if device not found in list of registered devices
> + *
> + * The callers are required to call dev_pm_opp_put() for the returned OPP after
> + * use.
> + */
> +struct dev_pm_opp *
> +dev_pm_opp_find_freq_exact_indexed(struct device *dev, unsigned long freq,
> + u32 index, bool available)
> +{
> + return _find_key_exact(dev, freq, index, available, _read_freq, NULL);
> +}
> +EXPORT_SYMBOL_GPL(dev_pm_opp_find_freq_exact_indexed);
> +
> static noinline struct dev_pm_opp *_find_freq_ceil(struct opp_table *opp_table,
> unsigned long *freq)
> {
> diff --git a/include/linux/pm_opp.h b/include/linux/pm_opp.h
> index a13a1705df57..23e4e4eaaa42 100644
> --- a/include/linux/pm_opp.h
> +++ b/include/linux/pm_opp.h
> @@ -124,6 +124,10 @@ struct dev_pm_opp *dev_pm_opp_find_freq_exact(struct device *dev,
> unsigned long freq,
> bool available);
>
> +struct dev_pm_opp *
> +dev_pm_opp_find_freq_exact_indexed(struct device *dev, unsigned long freq,
> + u32 index, bool available);
> +
> struct dev_pm_opp *dev_pm_opp_find_freq_floor(struct device *dev,
> unsigned long *freq);
>
> @@ -268,6 +272,13 @@ static inline struct dev_pm_opp *dev_pm_opp_find_freq_exact(struct device *dev,
> return ERR_PTR(-EOPNOTSUPP);
> }
>
> +static inline struct dev_pm_opp *
> +dev_pm_opp_find_freq_exact_indexed(struct device *dev, unsigned long freq,
> + u32 index, bool available)
> +{
> + return ERR_PTR(-EOPNOTSUPP);
> +}
> +
> static inline struct dev_pm_opp *dev_pm_opp_find_freq_floor(struct device *dev,
> unsigned long *freq)
> {
> --
> 2.31.1.272.g89b43f80a514
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2023-07-24 6:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 9:40 [PATCH 0/6] OPP: Indexed searching based on frequency Viresh Kumar
2023-07-21 9:40 ` [PATCH 1/6] OPP: Rearrange entries in pm_opp.h Viresh Kumar
2023-07-21 9:40 ` [PATCH 2/6] OPP: Introduce dev_pm_opp_find_freq_{ceil/floor}_indexed() APIs Viresh Kumar
2023-07-21 9:40 ` [PATCH 3/6] OPP: Introduce dev_pm_opp_get_freq_indexed() API Viresh Kumar
2023-07-21 9:40 ` [PATCH 4/6] OPP: Add dev_pm_opp_find_freq_exact_indexed() Viresh Kumar
2023-07-24 6:24 ` Manivannan Sadhasivam [this message]
2023-07-24 7:31 ` Viresh Kumar
2023-07-21 9:40 ` [PATCH 5/6] OPP: Update _read_freq() to return the correct frequency Viresh Kumar
2023-07-24 6:25 ` Manivannan Sadhasivam
2023-07-21 9:40 ` [PATCH 6/6] OPP: Reuse dev_pm_opp_get_freq_indexed() Viresh Kumar
2023-07-24 6:26 ` Manivannan Sadhasivam
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=20230724062405.GJ2370@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).