All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Dave Gerlach <d-gerlach@ti.com>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Rob Herring <robh+dt@kernel.org>, Keerthy J <j-keerthy@ti.com>,
	Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH v5 2/2] memory: ti-emif-sram: introduce relocatable suspend/resume handlers
Date: Mon, 16 Oct 2017 07:54:44 -0700	[thread overview]
Message-ID: <20171016145444.GX4394@atomide.com> (raw)
In-Reply-To: <20171013205915.9652-3-d-gerlach@ti.com>

* Dave Gerlach <d-gerlach@ti.com> [171013 14:00]:
> Certain SoCs like Texas Instruments AM335x and AM437x require parts
> of the EMIF PM code to run late in the suspend sequence from SRAM,
> such as saving and restoring the EMIF context and placing the memory
> into self-refresh.
> 
> One requirement for these SoCs to suspend and enter its lowest power
> mode, called DeepSleep0, is that the PER power domain must be shut off.
> Because the EMIF (DDR Controller) resides within this power domain, it
> will lose context during a suspend operation, so we must save it so we
> can restore once we resume. However, we cannot execute this code from
> external memory, as it is not available at this point, so the code must
> be executed late in the suspend path from SRAM.
> 
> This patch introduces a ti-emif-sram driver that includes several
> functions written in ARM ASM that are relocatable so the PM SRAM
> code can use them. It also allocates a region of writable SRAM to
> be used by the code running in the executable region of SRAM to save
> and restore the EMIF context. It can export a table containing the
> absolute addresses of the available PM functions so that other SRAM
> code can branch to them. This code is required for suspend/resume on
> AM335x and AM437x to work.
> 
> In addition to this, to be able to share data structures between C and
> the ti-emif-sram-pm assembly code, we can automatically generate all of
> the C struct member offsets and sizes as macros by processing
> emif-asm-offsets.c into assembly code and then extracting the relevant
> data as is done for the generated platform asm-offsets.h files.
> 
> Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
> ---
> v4->v5:
> * Simplify Makefile to generate include/generated/ti-emif-asm-offsets.h

Looks good to me:

Acked-by: Tony Lindgren <tony@atomide.com>

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/2] memory: ti-emif-sram: introduce relocatable suspend/resume handlers
Date: Mon, 16 Oct 2017 07:54:44 -0700	[thread overview]
Message-ID: <20171016145444.GX4394@atomide.com> (raw)
In-Reply-To: <20171013205915.9652-3-d-gerlach@ti.com>

* Dave Gerlach <d-gerlach@ti.com> [171013 14:00]:
> Certain SoCs like Texas Instruments AM335x and AM437x require parts
> of the EMIF PM code to run late in the suspend sequence from SRAM,
> such as saving and restoring the EMIF context and placing the memory
> into self-refresh.
> 
> One requirement for these SoCs to suspend and enter its lowest power
> mode, called DeepSleep0, is that the PER power domain must be shut off.
> Because the EMIF (DDR Controller) resides within this power domain, it
> will lose context during a suspend operation, so we must save it so we
> can restore once we resume. However, we cannot execute this code from
> external memory, as it is not available at this point, so the code must
> be executed late in the suspend path from SRAM.
> 
> This patch introduces a ti-emif-sram driver that includes several
> functions written in ARM ASM that are relocatable so the PM SRAM
> code can use them. It also allocates a region of writable SRAM to
> be used by the code running in the executable region of SRAM to save
> and restore the EMIF context. It can export a table containing the
> absolute addresses of the available PM functions so that other SRAM
> code can branch to them. This code is required for suspend/resume on
> AM335x and AM437x to work.
> 
> In addition to this, to be able to share data structures between C and
> the ti-emif-sram-pm assembly code, we can automatically generate all of
> the C struct member offsets and sizes as macros by processing
> emif-asm-offsets.c into assembly code and then extracting the relevant
> data as is done for the generated platform asm-offsets.h files.
> 
> Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
> ---
> v4->v5:
> * Simplify Makefile to generate include/generated/ti-emif-asm-offsets.h

Looks good to me:

Acked-by: Tony Lindgren <tony@atomide.com>

  reply	other threads:[~2017-10-16 14:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13 20:59 [PATCH v5 0/2] memory: Introduce ti-emif-sram driver Dave Gerlach
2017-10-13 20:59 ` Dave Gerlach
2017-10-13 20:59 ` Dave Gerlach
     [not found] ` <20171013205915.9652-1-d-gerlach-l0cyMroinI0@public.gmane.org>
2017-10-13 20:59   ` [PATCH v5 1/2] Documentation: dt: Update ti,emif bindings Dave Gerlach
2017-10-13 20:59     ` Dave Gerlach
2017-10-13 20:59     ` Dave Gerlach
2017-10-13 20:59 ` [PATCH v5 2/2] memory: ti-emif-sram: introduce relocatable suspend/resume handlers Dave Gerlach
2017-10-13 20:59   ` Dave Gerlach
2017-10-13 20:59   ` Dave Gerlach
2017-10-16 14:54   ` Tony Lindgren [this message]
2017-10-16 14:54     ` Tony Lindgren
     [not found]   ` <20171013205915.9652-3-d-gerlach-l0cyMroinI0@public.gmane.org>
2017-10-16 15:31     ` Santosh Shilimkar
2017-10-16 15:31       ` Santosh Shilimkar
2017-10-16 15:31       ` Santosh Shilimkar
2017-11-10 16:39       ` Russell King - ARM Linux
2017-11-10 16:39         ` Russell King - ARM Linux
2017-11-13 17:07         ` Santosh Shilimkar
2017-11-13 17:07           ` Santosh Shilimkar
2017-11-13 17:07           ` Santosh Shilimkar

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=20171016145444.GX4394@atomide.com \
    --to=tony@atomide.com \
    --cc=d-gerlach@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=j-keerthy@ti.com \
    --cc=johan@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=robh+dt@kernel.org \
    --cc=ssantosh@kernel.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.