From: Tony Lindgren <tony@atomide.com>
To: Dave Gerlach <d-gerlach@ti.com>
Cc: Keerthy J <j-keerthy@ti.com>,
linux-omap@vger.kernel.org, Brad Griffis <bgriffis@ti.com>,
linux-arm-kernel@lists.infradead.org,
Santosh Shilimkar <ssantosh@kernel.org>
Subject: Re: [PATCH 1/2] memory: ti-emif-sram: Add ti_emif_run_hw_leveling for DDR3 hardware leveling
Date: Tue, 2 Apr 2019 10:24:01 -0700 [thread overview]
Message-ID: <20190402172401.GO49658@atomide.com> (raw)
In-Reply-To: <20190402165743.28106-2-d-gerlach@ti.com>
* Dave Gerlach <d-gerlach@ti.com> [190402 16:57]:
> In certain situations, such as when returning from low power modes, the
> EMIF must re-run hardware leveling to properly restore DDR3 access.
>
> This is accomplished by introducing a new ti-emif-sram-pm call,
> ti_emif_run_hw_leveling, to check if DDR3 is in use and if so, trigger
> the full write and read leveling processes.
OK nice that you also consider devices with LPDDR2 then in case we
start seeing those.
Regards,
Tony
next prev parent reply other threads:[~2019-04-02 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 16:57 [PATCH 0/2] ARM: OMAP2+: AM43x: Support DDR HW leveling suspend/resume Dave Gerlach
2019-04-02 16:57 ` [PATCH 1/2] memory: ti-emif-sram: Add ti_emif_run_hw_leveling for DDR3 hardware leveling Dave Gerlach
2019-04-02 17:24 ` Tony Lindgren [this message]
2019-04-08 18:32 ` Dave Gerlach
2019-04-08 19:34 ` Tony Lindgren
2019-04-09 15:19 ` Tony Lindgren
2019-04-09 15:26 ` santosh.shilimkar
2019-04-09 15:33 ` Tony Lindgren
2019-04-02 16:57 ` [PATCH 2/2] ARM: OMAP2+: sleep43xx: Run EMIF HW leveling on resume path Dave Gerlach
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=20190402172401.GO49658@atomide.com \
--to=tony@atomide.com \
--cc=bgriffis@ti.com \
--cc=d-gerlach@ti.com \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.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 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).