From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/5] ARM: Alpine: smp support
Date: Sat, 31 Jan 2015 10:42:22 +0000 [thread overview]
Message-ID: <20150131104222.GS26493@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <54cc931d.9PqMlkwMeqHvUr4h%tsahee@annapurnalabs.com>
On Sat, Jan 31, 2015 at 10:32:29AM +0200, Tsahee Zidenberg wrote:
> +#include <linux/of.h>
> +#include <linux/of_address.h>
> +#include <linux/regmap.h>
> +#include <linux/mfd/syscon.h>
> +
> +#include <asm/io.h>
linux/io.h please.
> +
> +#include "alpine_cpu_pm.h"
> +#include "alpine_cpu_resume.h"
> +
> +/* NB registers */
> +#define AL_SYSFAB_POWER_CONTROL(cpu) (0x2000 + (cpu)*0x100 + 0x20)
> +
> +static struct regmap *al_sysfabric;
> +static struct al_cpu_resume_regs __iomem *al_cpu_resume_regs;
> +static int wakeup_supported;
> +
> +int alpine_cpu_wakeup(unsigned int phys_cpu, uint32_t phys_resume_addr)
> +{
> + if (!wakeup_supported)
> + return -ENOSYS;
> +
> + /* Set CPU resume address -
> + * secure firmware running on boot will jump to this address
> + * after setting proper CPU mode, and initialiing e.g. secure regs
> + * (the same mode all CPUs are booted to - usually HYP) */
Please stick to the kernel coding style:
/*
* Set CPU resume address -
* secure firmware running on boot will jump to this address
* after setting proper CPU mode, and initialiing e.g. secure regs
* (the same mode all CPUs are booted to - usually HYP)
*/
and you might as well move "regs" to the next line to even up the line
length between each line.
> + writel(phys_resume_addr,
> + &al_cpu_resume_regs->per_cpu[phys_cpu].resume_addr);
> +
> + /* Power-up the CPU */
> + regmap_write(al_sysfabric, AL_SYSFAB_POWER_CONTROL(phys_cpu), 0);
> +
> + return 0;
> +}
> +
> +void __init alpine_cpu_pm_init(void)
> +{
> + struct device_node *np;
> + uint32_t watermark;
> +
> + al_sysfabric = syscon_regmap_lookup_by_compatible("al,alpine-sysfabric-service");
> +
> + np = of_find_compatible_node(NULL, NULL, "al,alpine-cpu-resume");
What if "np" is NULL?
> + al_cpu_resume_regs = of_iomap(np, 0);
> +
> + wakeup_supported = (!IS_ERR(al_sysfabric)) && al_cpu_resume_regs;
wakeup_supported = !IS_ERR(al_sysfabric) && al_cpu_resume_regs;
is entirely sufficient - no need for additional parens.
> +
> + if (wakeup_supported) {
> + watermark = readl(&al_cpu_resume_regs->watermark);
> + wakeup_supported = ((watermark & AL_CPU_RESUME_MAGIC_NUM_MASK)
> + == AL_CPU_RESUME_MAGIC_NUM);
wakeup_supported = (watermark & AL_CPU_RESUME_MAGIC_NUM_MASK)
== AL_CPU_RESUME_MAGIC_NUM;
is also sufficient.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-01-31 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 8:32 [PATCH v2 3/5] ARM: Alpine: smp support Tsahee Zidenberg
2015-01-31 10:42 ` Russell King - ARM Linux [this message]
2015-01-31 20:11 ` Tsahee Zidenberg
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=20150131104222.GS26493@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).