public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	Tom Rini <trini@konsulko.com>
Cc: Simon Glass <sjg@chromium.org>,
	Mattijs Korpershoek <mkorpershoek@kernel.org>,
	u-boot@lists.denx.de,
	Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Subject: Re: [PATCH 1/1] doc: u-boot-test-reset: mention power cycling
Date: Mon, 05 May 2025 11:28:48 +0200	[thread overview]
Message-ID: <874ixz76en.fsf@kernel.org> (raw)
In-Reply-To: <20250503101237.48135-1-heinrich.schuchardt@canonical.com>

Hi Heinrich,

Thank you for the patch.

On sam., mai 03, 2025 at 12:12, Heinrich Schuchardt <heinrich.schuchardt@canonical.com> wrote:

> Using power cycling is a valid option to implement u-boot-test-reset.
>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>

Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>

> ---
>  doc/develop/py_testing.rst | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/doc/develop/py_testing.rst b/doc/develop/py_testing.rst
> index 824e3c0d9a7..33103bbd650 100644
> --- a/doc/develop/py_testing.rst
> +++ b/doc/develop/py_testing.rst
> @@ -377,7 +377,8 @@ this script again to restore U-Boot to an operational state before running the
>  next test function.
>  
>  This script will likely be implemented by communicating with some form of
> -relay or electronic switch attached to the board's reset signal.
> +relay or electronic switch attached to the board's reset signal. Power cycling
> +is another option.
>  
>  The semantics of this script require that when it is executed, U-Boot will
>  start running from scratch. If the U-Boot binary to be tested has been written
> -- 
> 2.48.1

      reply	other threads:[~2025-05-05  9:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-03 10:12 [PATCH 1/1] doc: u-boot-test-reset: mention power cycling Heinrich Schuchardt
2025-05-05  9:28 ` Mattijs Korpershoek [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=874ixz76en.fsf@kernel.org \
    --to=mkorpershoek@kernel.org \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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