From: Viresh Kumar <viresh.kumar@linaro.org>
To: Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@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>,
niklas.cassel@linaro.org, d-gerlach@ti.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/4] OPP: Return error on error from dev_pm_opp_get_opp_count()
Date: Thu, 4 Oct 2018 09:46:21 +0530 [thread overview]
Message-ID: <09f662f95306f3e3d47ab6842bc4b0bb868a80ad.1538625101.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1538625101.git.viresh.kumar@linaro.org>
Return error number instead of 0 on failures.
Fixes: a1e8c13600bf ("PM / OPP: "opp-hz" is optional for power domains")
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
drivers/opp/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/opp/core.c b/drivers/opp/core.c
index cdf918aaac34..2c2df4e4fc14 100644
--- a/drivers/opp/core.c
+++ b/drivers/opp/core.c
@@ -318,7 +318,7 @@ int dev_pm_opp_get_opp_count(struct device *dev)
count = PTR_ERR(opp_table);
dev_dbg(dev, "%s: OPP table not found (%d)\n",
__func__, count);
- return 0;
+ return count;
}
count = _get_opp_count(opp_table);
--
2.18.0.rc1.242.g61856ae69a2c
next prev parent reply other threads:[~2018-10-04 4:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 4:16 [PATCH 0/4] OPP: Fix more bugs and improve error handling Viresh Kumar
2018-10-04 4:16 ` [PATCH 1/4] OPP: Improve error handling in dev_pm_opp_of_cpumask_add_table() Viresh Kumar
2018-10-04 4:16 ` Viresh Kumar [this message]
2018-10-04 4:16 ` [PATCH 3/4] cpufreq: dt: Try freeing static OPPs only if we have added them Viresh Kumar
2018-10-04 4:16 ` [PATCH V2 4/4] PM / OPP: _of_add_opp_table_v2(): increment count only if OPP is added 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=09f662f95306f3e3d47ab6842bc4b0bb868a80ad.1538625101.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=d-gerlach@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=niklas.cassel@linaro.org \
--cc=nm@ti.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
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).