Hi,
On 2019/02/19 18:21, Arnd Bergmann wrote:
On Tue, Feb 19, 2019 at 8:12 AM Sugaya, Taichi
wrote:
On 2019/02/18 21:15, Arnd Bergmann wrote:
On Fri, Feb 8, 2019 at 1:26 PM Sugaya Taichi
wrote:
+static int __init m10v_pm_init(void)
+{
+ suspend_set_ops(_pm_ops);
+
+ return 0;
On Tue, Feb 19, 2019 at 8:12 AM Sugaya, Taichi
wrote:
> On 2019/02/18 21:15, Arnd Bergmann wrote:
> > On Fri, Feb 8, 2019 at 1:26 PM Sugaya Taichi
> > wrote:
>
> >> +static int __init m10v_pm_init(void)
> >> +{
> >> + suspend_set_ops(_pm_ops);
> >> +
> >> + return 0;
> >> +}
> >>
Hi,
Thank you for your comments.
On 2019/02/18 21:15, Arnd Bergmann wrote:
On Fri, Feb 8, 2019 at 1:26 PM Sugaya Taichi
wrote:
+static int m10v_pm_enter(suspend_state_t state)
+{
+ switch (state) {
+ case PM_SUSPEND_STANDBY:
+ pr_err("STANDBY\n");
+
On Fri, Feb 8, 2019 at 1:26 PM Sugaya Taichi
wrote:
> +static int m10v_pm_enter(suspend_state_t state)
> +{
> + switch (state) {
> + case PM_SUSPEND_STANDBY:
> + pr_err("STANDBY\n");
> + asm("wfi");
> + break;
> + case PM_SUSPEND_MEM:
>
This adds the basic M10V SoC support under arch/arm.
Since all cores are activated in the custom bootloader before booting
linux, it is necessary to wait for the secondary-cores using cpu-enable-
method and special sram.
Signed-off-by: Sugaya Taichi
---
arch/arm/Kconfig | 2 +
5 matches
Mail list logo