From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 2/2] drivers: firmware: psci: checker: Use psci_is_available()
Date: Wed, 11 Oct 2017 10:03:02 +0200 [thread overview]
Message-ID: <1507708982-12336-3-git-send-email-geert+renesas@glider.be> (raw)
In-Reply-To: <1507708982-12336-1-git-send-email-geert+renesas@glider.be>
Use the psci_is_available() helper instead of direct accesses to
psci_ops internals.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
drivers/firmware/psci_checker.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/firmware/psci_checker.c b/drivers/firmware/psci_checker.c
index 6523ce9628659755..72b40ed2dcce7cf4 100644
--- a/drivers/firmware/psci_checker.c
+++ b/drivers/firmware/psci_checker.c
@@ -54,7 +54,7 @@ static int psci_ops_check(void)
int migrate_type = -1;
int cpu;
- if (!(psci_ops.cpu_off && psci_ops.cpu_on && psci_ops.cpu_suspend)) {
+ if (!psci_is_available()) {
pr_warn("Missing PSCI operations, aborting tests\n");
return -EOPNOTSUPP;
}
--
2.7.4
prev parent reply other threads:[~2017-10-11 11:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 8:03 [PATCH 0/2] drivers: firmware: psci: Extract psci_is_available() helper Geert Uytterhoeven
2017-10-11 8:03 ` Geert Uytterhoeven
2017-10-11 8:03 ` [PATCH 1/2] drivers: firmware: psci: Add psci_is_available() Geert Uytterhoeven
2017-10-11 8:03 ` Geert Uytterhoeven
2017-10-12 2:58 ` Jisheng Zhang
2017-10-12 2:58 ` Jisheng Zhang
2017-10-12 6:58 ` Geert Uytterhoeven
2017-10-12 6:58 ` Geert Uytterhoeven
2017-10-12 6:58 ` Geert Uytterhoeven
2017-10-25 15:45 ` [1/2] " Lorenzo Pieralisi
2017-10-25 15:45 ` Lorenzo Pieralisi
2017-10-11 8:03 ` Geert Uytterhoeven [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=1507708982-12336-3-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.