public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Liam Beguin <liambeguin@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/8] add inital SF tests
Date: Sun,  4 Mar 2018 23:21:59 -0500	[thread overview]
Message-ID: <20180305042206.25638-1-liambeguin@gmail.com> (raw)

Hi all,

This is the inital step to adding tests for the SF subsystem plus very
minor fixes. It is based on work I found on the mailing list[1].
For now, it doesn't do much but I plan on adding code to reset the flash
to its initial state (based on an env flag) and more code to test the
`sf protect` subcommand (which is the main goal of this series).
I'm sending it now to make sure it's headed in the right direction.

Base on Stephen's comment[2], I haven't added the radomized features.
I'll see how this iteration goes and maybe add it later.

Changes since v1:
 - remove unnecessary skip flag from environment
 - move crc32() to u_boot_utils.py and add extra checks
 - rewrite sf_prepare to return a dict of parameter
 - use assert instead of pytest.fail
 - remove verbose from sf_prepare()
 - update documentation
 - improve readability
 - use ' consistently instead of "
 - use sf_read() in test_sf_read()
 - rename crc variables
 - add speed parameter with optional random range
 - allow `sf read` to write at 0x00

Thanks,
Liam Beguin

[ 1 ] https://patchwork.ozlabs.org/patch/623061/
[ 2 ] https://lists.denx.de/pipermail/u-boot/2018-March/321688.html

Liam Beguin (8):
  spi: spi_flash: do not fail silently on bad user input
  cmd: sf: fix map_physmem check
  test/py: README: fix typo
  test/py: README: add HOSTNAME to PYTHONPATH
  test/py: do not import pytest multiple times
  test/py: add generic CRC32 function
  test/py: add spi_flash tests

 cmd/sf.c                    |   2 +-
 drivers/mtd/spi/spi_flash.c |   2 +-
 test/py/README.md           |   6 +-
 test/py/tests/test_sf.py    | 223 ++++++++++++++++++++++++++++++++++++++++++++
 test/py/u_boot_utils.py     |  24 ++++-
 5 files changed, 251 insertions(+), 6 deletions(-)
 create mode 100644 test/py/tests/test_sf.py


base-commit: 77bba970e2372b01156c66585db3d6fc751c7178
Published-As: https://github.com/Liambeguin/u-boot/releases/tag/test_sf-v2

-- 
2.16.1.72.g5be1f00a9a70

             reply	other threads:[~2018-03-05  4:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05  4:21 Liam Beguin [this message]
2018-03-05  4:22 ` [U-Boot] [PATCH v2 1/7] spi: spi_flash: do not fail silently on bad user input Liam Beguin
2018-03-05  4:22 ` [U-Boot] [PATCH v2 2/7] cmd: sf: fix map_physmem check Liam Beguin
2018-03-05  4:22 ` [U-Boot] [PATCH v2 3/7] test/py: README: fix typo Liam Beguin
2018-03-05  4:22 ` [U-Boot] [PATCH v2 4/7] test/py: README: add HOSTNAME to PYTHONPATH Liam Beguin
2018-03-05  4:22 ` [U-Boot] [PATCH v2 5/7] test/py: do not import pytest multiple times Liam Beguin
2018-03-05  4:22 ` [U-Boot] [PATCH v2 6/7] test/py: add generic CRC32 function Liam Beguin
2018-03-13 21:27   ` Stephen Warren
2018-03-05  4:22 ` [U-Boot] [PATCH v2 7/7] test/py: add spi_flash tests Liam Beguin
2018-03-13 21:41   ` Stephen Warren
2018-03-14  0:27     ` Liam Beguin
2018-03-12 22:59 ` [U-Boot] [PATCH v2 0/8] add inital SF tests Liam Beguin

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=20180305042206.25638-1-liambeguin@gmail.com \
    --to=liambeguin@gmail.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