[PATCH v22 11/11] acpi/arm64: Add SBSA Generic Watchdog support in GTDT driver

On Fri, Mar 31, 2017 at 04:10:43PM +0800, Fu Wei wrote:

[...]

quoted

quoted

+static int __init gtdt_sbsa_gwdt_init(void)
+{
+     int ret, i = 0;
+     void *platform_timer;
+     struct acpi_table_header *table;
+
+     if (acpi_disabled)
+             return 0;
+
+     if (ACPI_FAILURE(acpi_get_table(ACPI_SIG_GTDT, 0, &table)))
+             return -EINVAL;
+
+     ret = acpi_gtdt_init(table, NULL);
+     if (ret)
+             return ret;

Ok, I missed previous versions reviews so I miss the background
here and I apologise.

I do not understand why you call acpi_gtdt_init() again (or better,
why acpi_gtdt_init() does not return straight away) here if the
stashed pointer in acpi_gtdt_desc is already set. I am not a big fan
of the for_each_platform_timer macro either, here you can just read
the ACPI_SIG_GTDT and parse its entries, I see no point in calling
acpi_gtdt_init() again, there is nothing to stash for later probing,
is there ?

Or it is just to reuse common parsing code ? Regardless, if the
acpi_gtdt_desc struct is already initialized acpi_gtdt_init() should
just return or I am missing the point.

I would like clarifications on the acpi_gtdt_init() call above please
(plus GSI unmap fix), apart from that:

Reviewed-by: Lorenzo Pieralisi <redacted>

Actually, after the discussion in the 7th patch, I have tried to do
this, see if that can make the code simpler.
Then I found out that
(1) If we would like to reuse "for_each_platform_timer" (and
"next_platform_timer") to scan the GTDT for SBSA watchdog, we have to
re-initialize acpi_gtdt_desc, too.
     So we still need to explain that why we have to re-initialize
acpi_gtdt_desc.
(2) If we totally ignore acpi_gtdt_desc, and acpi_gtdt_init(), we
can't re-use  "for_each_platform_timer" (and "next_platform_timer") .
we have to re-write  the loop of scanning the GTDT for SBSA watchdog,

Or we get rid of for_each_platform_timer altogether that for me
is not useful at all and just obfuscates.

Anyway, add the comment below and you are done with this, at this point
in time it is best to avoid changing the code we'd just risk adding
bugs.

At -rc1 we will send patches to reshape this code as per this
discussion.

Thanks !
Lorenzo

So may I suggest that maybe we can keep using acpi_gtdt_init, only add
the comment to explain why we have to re-initialize
acpi_gtdt_desc(Just what you have said in the 7th patch. Thanks for
your correction for the comment, I will use that ), this way maybe can
make the code simpler.

But If you still concern about this,  we still can discuss this at -rc1.

Great thanks for your help! :-)

quoted

quoted

+     for_each_platform_timer(platform_timer) {
+             if (is_non_secure_watchdog(platform_timer)) {
+                     ret = gtdt_import_sbsa_gwdt(platform_timer, i);
+                     if (ret)
+                             break;
+                     i++;
+             }
+     }
+
+     if (i)
+             pr_info("found %d SBSA generic Watchdog(s).\n", i);
+
+     return ret;
+}
+
+device_initcall(gtdt_sbsa_gwdt_init);
--
2.9.3

-- 
Best regards,

Fu Wei
Software Engineer
Red Hat