powerpc/powernv: Check OPAL dump calls exist before using

Check that the OPAL_DUMP_READ token exists before initalising the elog
infrastructure.

This avoids littering the OPAL console with:
  "OPAL: Called with bad token 91"

Signed-off-by: Michael Neuling <mikey@neuling.org>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>

diff --git a/arch/powerpc/platforms/powernv/opal-dump.c b/arch/powerpc/platforms/powernv/opal-dump.c
index 3b819959337cc397ea14fcba040abdd2dbe79f79..23260f7dfa7aeca7446dcfcc6e59f5ced346e6b1 100644 (file)
--- a/arch/powerpc/platforms/powernv/opal-dump.c
+++ b/arch/powerpc/platforms/powernv/opal-dump.c
@@ -427,6 +427,10 @@ void __init opal_platform_dump_init(void)
 {
        int rc;
 
+       /* ELOG not supported by firmware */
+       if (!opal_check_token(OPAL_DUMP_READ))
+               return;
+
        dump_kset = kset_create_and_add("dump", NULL, opal_kobj);
        if (!dump_kset) {
                pr_warn("%s: Failed to create dump kset\n", __func__);