From: Viresh Kumar <viresh.kumar@linaro.org>
To: Nicola Mazzucato <nicola.mazzucato@arm.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, sudeep.holla@arm.com,
rjw@rjwysocki.net, vireshk@kernel.org, robh+dt@kernel.org,
sboyd@kernel.org, nm@ti.com, daniel.lezcano@linaro.org,
morten.rasmussen@arm.com, chris.redpath@arm.com
Subject: Re: [PATCH v3 2/3] opp/of: Allow empty opp-table with opp-shared
Date: Tue, 3 Nov 2020 10:31:41 +0530 [thread overview]
Message-ID: <20201103050141.kiuyotzt4brisch7@vireshk-i7> (raw)
In-Reply-To: <20201102120115.29993-3-nicola.mazzucato@arm.com>
On 02-11-20, 12:01, Nicola Mazzucato wrote:
> The opp binding now allows to have an empty opp table and shared-opp to
> merely describe a hw connection among devices (f/v lines).
>
> When initialising an opp table, allow such case by:
> - treating some errors as warnings
> - do not mark empty tables as shared
> - don't fail on empty table
>
> Signed-off-by: Nicola Mazzucato <nicola.mazzucato@arm.com>
> ---
> drivers/opp/of.c | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/opp/of.c b/drivers/opp/of.c
> index 874b58756220..b0230490bb31 100644
> --- a/drivers/opp/of.c
> +++ b/drivers/opp/of.c
> @@ -157,6 +157,11 @@ static void _opp_table_free_required_tables(struct opp_table *opp_table)
> /*
> * Populate all devices and opp tables which are part of "required-opps" list.
> * Checking only the first OPP node should be enough.
> + *
> + * Corner case: empty opp table and opp-shared found. In this case we set
> + * unconditionally the opp table access to exclusive, as the opp-shared property
> + * is used purely to describe hw connections. Such information will be retrieved
> + * via dev_pm_opp_of_get_sharing_cpus().
> */
> static void _opp_table_alloc_required_tables(struct opp_table *opp_table,
> struct device *dev,
> @@ -169,7 +174,9 @@ static void _opp_table_alloc_required_tables(struct opp_table *opp_table,
> /* Traversing the first OPP node is all we need */
> np = of_get_next_available_child(opp_np, NULL);
> if (!np) {
> - dev_err(dev, "Empty OPP table\n");
> + dev_warn(dev, "Empty OPP table\n");
> +
> + opp_table->shared_opp = OPP_TABLE_ACCESS_EXCLUSIVE;
I am not sure I understand the reasoning behind this.
> return;
> }
>
> @@ -377,7 +384,9 @@ int dev_pm_opp_of_find_icc_paths(struct device *dev,
> struct icc_path **paths;
>
> ret = _bandwidth_supported(dev, opp_table);
> - if (ret <= 0)
> + if (ret == -EINVAL)
> + return 0; /* Empty OPP table is a valid corner-case, let's not fail */
> + else if (ret <= 0)
> return ret;
>
> ret = 0;
> --
> 2.27.0
--
viresh
next prev parent reply other threads:[~2020-11-03 5:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 12:01 [PATCH v3 0/3] CPUFreq: Add support for cpu performance dependencies Nicola Mazzucato
2020-11-02 12:01 ` [PATCH v3 1/3] dt-bindings/opp: Update documentation for opp-shared Nicola Mazzucato
2020-11-02 12:01 ` [PATCH v3 2/3] opp/of: Allow empty opp-table with opp-shared Nicola Mazzucato
2020-11-03 5:01 ` Viresh Kumar [this message]
2020-11-04 17:54 ` Nicola Mazzucato
2020-11-05 4:41 ` Viresh Kumar
2020-11-16 11:45 ` Nicola Mazzucato
2020-11-02 12:01 ` [PATCH v3 3/3] [RFC] CPUFreq: Add support for cpu-perf-dependencies Nicola Mazzucato
2020-11-06 9:20 ` Viresh Kumar
2020-11-06 10:37 ` Lukasz Luba
2020-11-06 10:55 ` Viresh Kumar
2020-11-06 11:14 ` Lukasz Luba
2020-11-09 6:57 ` Viresh Kumar
2020-11-16 11:33 ` Lukasz Luba
2020-11-17 10:11 ` Viresh Kumar
2020-11-17 10:47 ` Nicola Mazzucato
2020-11-17 10:53 ` Viresh Kumar
2020-11-17 13:06 ` Rafael J. Wysocki
2020-11-18 4:42 ` Viresh Kumar
2020-11-18 12:00 ` Rafael J. Wysocki
2020-11-19 6:40 ` Viresh Kumar
2020-11-17 10:47 ` Lukasz Luba
2020-11-17 10:55 ` Viresh Kumar
2020-11-06 9:24 ` Viresh Kumar
2020-11-19 6:43 ` Viresh Kumar
2020-11-03 10:18 ` [PATCH v3 0/3] CPUFreq: Add support for cpu performance dependencies Viresh Kumar
2020-11-04 18:04 ` Nicola Mazzucato
2020-11-05 14:25 ` Vincent Guittot
2020-11-05 15:46 ` Ionela Voinescu
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=20201103050141.kiuyotzt4brisch7@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=chris.redpath@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=nicola.mazzucato@arm.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sudeep.holla@arm.com \
--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).