On Tue, Sep 8, 2015 at 12:03 PM, Leif Lindholm leif.lindholm@linaro.org wrote:
On Tue, Sep 08, 2015 at 02:09:51PM +0100, Mark Rutland wrote:
On Tue, Sep 08, 2015 at 01:43:35PM +0100, Leif Lindholm wrote:
The ACPI DBG2 table defines a debug console. Add support for parsing it and using it to select earlycon destination when no arguments provided.
Signed-off-by: Leif Lindholm leif.lindholm@linaro.org
[...]
diff --git a/drivers/acpi/console.c b/drivers/acpi/console.c new file mode 100644 index 0000000..a985890 --- /dev/null +++ b/drivers/acpi/console.c @@ -0,0 +1,103 @@ +/*
- Copyright (c) 2012, Intel Corporation
- Copyright (c) 2015, Linaro Ltd.
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License version 2 as
- published by the Free Software Foundation.
- */
+#define DEBUG
Why?
Kept around from Lv Zheng's 2012 set. Will drop.
+#define pr_fmt(fmt) "ACPI: " KBUILD_MODNAME ": " fmt
+#include <linux/acpi.h> +#include <linux/kernel.h> +#include <linux/serial_core.h>
+#define NUM_ELEMS(x) (sizeof(x) / sizeof(*x))
Use ARRAY_SIZE (from kernel.h).
I was sure there was something like that, but my grep-fu failed me. Will fix.
+#ifdef CONFIG_SERIAL_EARLYCON +static int use_earlycon __initdata; +static int __init setup_acpi_earlycon(char *buf) +{
- if (!buf)
use_earlycon = 1;- return 0;
+} +early_param("earlycon", setup_acpi_earlycon);
It seems a shame to add this after folding the OF case into the earlycon code. What necessitates this being a separate early_param? Why is it too early to parse DBG2?
Currently, we don't even know where our ACPI tables are at this point (efi_init() is called two functions after parse_early_param() in setup_arch). More specifically, because acpi_boot_table_init() is called even later than that.
If we moved both of those earlier, we could drop the extra earlycon param handling for ACPI. That would of course reduce the ability to have dynamically configurable debug messages for both of these.
Personally, I liked that we don't have to have the early_param handling globally located. I'm not sure I see the benefit of centralizing it especially if it doesn't even help for your case.
Rob
-
Rob Herring