All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Andrew F. Davis" <afd@ti.com>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
	"Kevin Hilman" <khilman@kernel.org>,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] ARM: OMAP: Wakeupgen: AM43xx HS devices should save context like non-HS
Date: Tue, 9 Apr 2019 08:08:56 -0700	[thread overview]
Message-ID: <20190409150856.GH2839@atomide.com> (raw)
In-Reply-To: <20190329175336.19824-4-afd@ti.com>

* Andrew F. Davis <afd@ti.com> [190329 17:53]:
> Unlike some previous generation devices, AM43xx HS IRQ and Wakegen
> context is handled by the ROM for us, and no secure service call
> is needed or supported. Non-GP AM43xx devices should take the
> same path as GP.

Applying the two SoC related changes into omap-for-v5.2/soc.

Tony

  reply	other threads:[~2019-04-09 15:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 17:53 [PATCH 1/5] ARM: dts: am43xx-epos-evm: Keep DCDC5 and DCDC6 always on Andrew F. Davis
2019-03-29 17:53 ` Andrew F. Davis
2019-03-29 17:53 ` [PATCH 2/5] ARM: dts: am43xx-epos-evm: Keep DCDC3 regulator on in suspend to memory Andrew F. Davis
2019-03-29 17:53   ` Andrew F. Davis
2019-03-29 17:53 ` [PATCH 3/5] ARM: dts: am43xx-epos-evm: Add matrix keypad as wakeup source Andrew F. Davis
2019-03-29 17:53   ` Andrew F. Davis
2019-03-29 17:53 ` [PATCH 4/5] ARM: OMAP: Wakeupgen: AM43xx HS devices should save context like non-HS Andrew F. Davis
2019-03-29 17:53   ` Andrew F. Davis
2019-04-09 15:08   ` Tony Lindgren [this message]
2019-03-29 17:53 ` [PATCH 5/5] ARM: OMAP2+: pm33xx-core: Do not Turn OFF CEFUSE as PPA may be using it Andrew F. Davis
2019-03-29 17:53   ` Andrew F. Davis
2019-04-09 15:08 ` [PATCH 1/5] ARM: dts: am43xx-epos-evm: Keep DCDC5 and DCDC6 always on Tony Lindgren

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=20190409150856.GH2839@atomide.com \
    --to=tony@atomide.com \
    --cc=afd@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=khilman@kernel.org \
    --cc=linux-kernel@vger.kernel.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 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.