All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Hogan <james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
To: Paul Bolle <pebolle-IWqWACnzNjzz+pZb47iToQ@public.gmane.org>
Cc: linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: metag: CONFIG_METAG_SUSPEND_MEM
Date: Tue, 20 May 2014 11:00:00 +0100	[thread overview]
Message-ID: <537B27A0.2010204@imgtec.com> (raw)
In-Reply-To: <1400576897.4912.20.camel@x220>

Hi Paul,

On 20/05/14 10:08, Paul Bolle wrote:
> There are a number of checks for CONFIG_METAG_SUSPEND_MEM in metag's
> code. But there's no Kconfig symbol METAG_SUSPEND_MEM. That means
> there's quite bit of code currently hidden by those checks (from a patch
> I drafted before sending this message):
>     arch/metag/include/asm/irq.h    |   5 ---
>     arch/metag/kernel/Makefile      |   1 -
>     arch/metag/kernel/traps.c       |  38 ----------------------
>     arch/metag/mm/mmu-meta2.c       |  18 -----------
>     drivers/irqchip/irq-metag-ext.c | 196 --------------------------------------------------------------------------------------------------------------
>     5 files changed, 258 deletions(-)
> 
> I assume people are still working on that code, and that
> METAG_SUSPEND_MEM will be added in some future release. Am I right?

That was the plan, yes. The TZ1090 SoC can do suspend to RAM, but not in
mainline yet, so there are a few loose ends still.

I'll have a look at what we can do to sort it out. I have a work in
progress patchset somewhere to add the suspend support to mainline, then
at least the code could be enabled.

Thanks for pointing it out.

Cheers
James
--
To unsubscribe from this list: send the line "unsubscribe linux-metag" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2014-05-20 10:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20  9:08 metag: CONFIG_METAG_SUSPEND_MEM Paul Bolle
2014-05-20 10:00 ` James Hogan [this message]

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=537B27A0.2010204@imgtec.com \
    --to=james.hogan-1axoqhu6uovqt0dzr+alfa@public.gmane.org \
    --cc=linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pebolle-IWqWACnzNjzz+pZb47iToQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.