From: Tony Lindgren <tony@atomide.com>
To: Dave Gerlach <d-gerlach@ti.com>
Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
Johan Hovold <johan@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Keerthy J <j-keerthy@ti.com>
Subject: Re: [PATCH 0/9] ARM: dts: am33xx/am4372: Add suspend-resume support
Date: Tue, 27 Feb 2018 09:46:31 -0800 [thread overview]
Message-ID: <20180227174631.GD5448@atomide.com> (raw)
In-Reply-To: <1519011305-17822-1-git-send-email-d-gerlach@ti.com>
* Dave Gerlach <d-gerlach@ti.com> [180218 19:35]:
> Hi,
> This series is the last needed to enable suspend/resume on am335x/am437x
> along with [1]. It adds required dt nodes for the emif and core PM code
> to find the needed sram nodes and marks key devices with ti,no-idle so
> that the kernel does not idle them. With this suspend to mem can be achieved
> by following the steps described in [1].
Applying all these into omap-for-v4.17/dt thanks.
Tony
prev parent reply other threads:[~2018-02-27 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 3:34 [PATCH 0/9] ARM: dts: am33xx/am4372: Add suspend-resume support Dave Gerlach
2018-02-19 3:34 ` [PATCH 1/9] ARM: dts: am33xx: Reserve pm code and data regions in ocmcram sram node Dave Gerlach
2018-02-19 3:34 ` [PATCH 2/9] ARM: dts: am4372: " Dave Gerlach
2018-02-19 3:34 ` [PATCH 3/9] ARM: dts: am33xx: Update emif node Dave Gerlach
2018-02-19 3:35 ` [PATCH 4/9] ARM: dts: am4372: " Dave Gerlach
2018-02-19 3:35 ` [PATCH 5/9] ARM: dts: am33xx: Add pm-sram phandle to soc node Dave Gerlach
2018-02-19 3:35 ` [PATCH 6/9] ARM: dts: am4372: Add " Dave Gerlach
2018-02-19 3:35 ` [PATCH 7/9] ARM: dts: am33xx: Mark emif with ti,no-idle Dave Gerlach
2018-02-19 3:35 ` [PATCH 8/9] ARM: dts: am4372: " Dave Gerlach
2018-02-19 3:35 ` [PATCH 9/9] ARM: dts: am4372: Mark omap_l3_noc " Dave Gerlach
2018-02-27 17:46 ` Tony Lindgren [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=20180227174631.GD5448@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-omap@vger.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).