From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM64: kernel: unify ACPI and DT cpus initialization
Date: Mon, 11 May 2015 17:29:45 +0100 [thread overview]
Message-ID: <20150511162945.GD4595@leverpostej> (raw)
In-Reply-To: <1431020084-5875-2-git-send-email-lorenzo.pieralisi@arm.com>
Hi Lorenzo,
> + enable_method = acpi_get_enable_method(cpu);
> + if (!enable_method)
> + pr_err("Undefined ACPI enable-method\n");
I was going to complain that "enable-method" is a DT term that doesn't
strictly apply to ACPI, but ACPI doesn't seem to have its own
terminology for this, so I guess this is ok.
However, I'd recommend replacing "Undefined" with "Unknown/Unsupported"
in the log message.
[...]
> +static u64 __init of_get_cpu_mpidr(struct device_node *dn)
> +{
> + const u32 *cell;
> + u64 hwid;
> +
> + /*
> + * A cpu node with missing "reg" property is
> + * considered invalid to build a cpu_logical_map
> + * entry.
> + */
> + cell = of_get_property(dn, "reg", NULL);
> + if (!cell) {
> + pr_err("%s: missing reg property\n", dn->full_name);
> + return INVALID_HWID;
> + }
> +
> + hwid = of_read_number(cell, of_n_addr_cells(dn));
Existing bug, but cell should be a __be32 pointer rather than a u32
pointer (as that's what of_read_number expects).
Other than that, this looks fine to me:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Tested-by: Mark Rutland <mark.rutland@arm.com> [DT]
Thanks,
Mark.
next prev parent reply other threads:[~2015-05-11 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 17:34 [PATCH 1/2] ARM64: kernel: make cpu_ops hooks DT agnostic Lorenzo Pieralisi
2015-05-07 17:34 ` [PATCH 2/2] ARM64: kernel: unify ACPI and DT cpus initialization Lorenzo Pieralisi
2015-05-11 16:29 ` Mark Rutland [this message]
2015-05-12 10:37 ` Lorenzo Pieralisi
2015-05-11 16:04 ` [PATCH 1/2] ARM64: kernel: make cpu_ops hooks DT agnostic Mark Rutland
2015-05-12 1:31 ` Hanjun Guo
2015-05-12 10:45 ` Lorenzo Pieralisi
2015-05-12 13:43 ` Hanjun Guo
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=20150511162945.GD4595@leverpostej \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.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