mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Drew Fustini <dfustini@baylibre.com>,
	Santosh Shilimkar <ssantosh@kernel.org>
Cc: Nishanth Menon <nm@ti.com>, <linux-kernel@vger.kernel.org>,
	Dave Gerlach <d-gerlach@ti.com>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] soc: ti: wkup_m3_ipc: Add debug option to halt m3 in suspend
Date: Tue, 3 May 2022 08:09:48 -0500	[thread overview]
Message-ID: <165158335751.6631.17627635090230319149.b4-ty@ti.com> (raw)
In-Reply-To: <20220502033211.1383158-1-dfustini@baylibre.com>

Hi Drew Fustini,

On Sun, 1 May 2022 20:32:12 -0700, Drew Fustini wrote:
> From: Dave Gerlach <d-gerlach@ti.com>
> 
> Add a debugfs option to allow configurable halting of the wkup_m3
> during suspend at the last possible point before low power mode entry.
> This condition can only be resolved through JTAG and advancing beyond
> the while loop in a8_lp_ds0_handler [1]. Although this hangs the system
> it forces the system to remain active once it has been entirely
> configured for low power mode entry, allowing for register inspection
> through JTAG to help in debugging transition errors.
> 
> [...]

I have applied the following to branch ti-drivers-soc-next on [1].
Thank you!

[1/1] soc: ti: wkup_m3_ipc: Add debug option to halt m3 in suspend
      commit: 2a21f9e6d9a408dbd09a01caf5fff42c2f70fa82

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D


      reply	other threads:[~2022-05-03 13:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02  3:32 Drew Fustini
2022-05-03 13:09 ` Nishanth Menon [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=165158335751.6631.17627635090230319149.b4-ty@ti.com \
    --to=nm@ti.com \
    --cc=d-gerlach@ti.com \
    --cc=dfustini@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®