U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Simon Glass <sjg@chromium.org>, Love Kumar <love.kumar@amd.com>
Cc: u-boot@lists.denx.de, git@xilinx.com
Subject: Re: [PATCH v2] test/py: spi: Add tests for SPI flash device
Date: Tue, 30 Jul 2024 11:04:20 +0200	[thread overview]
Message-ID: <b68ec280-bd16-4977-af34-3ef8ba59d30e@amd.com> (raw)
In-Reply-To: <CAFLszTiMk_oJTwU8K4CZGJa9FXnSgkJs2xgcD0fAWz_9iPjftQ@mail.gmail.com>



On 7/28/24 21:36, Simon Glass wrote:
> Hi Love,
> 
> On Wed, 24 Jul 2024 at 05:07, Love Kumar <love.kumar@amd.com> wrote:
>>
>> Add test cases for sf commands to verify various SPI flash operations
>> such as erase, write and read. It also adds qspi lock unlock cases.
>> This test relies on boardenv_* configurations to run it for different
>> SPI flash family such as single SPI, QSPI, and OSPI.
>>
>> Signed-off-by: Love Kumar <love.kumar@amd.com>
>> ---
>> Changes in v2:
>>   - Fix the pylint errors
>>   - Re-order/organize the tests
>> ---
>>   test/py/tests/test_spi.py | 680 ++++++++++++++++++++++++++++++++++++++
>>   1 file changed, 680 insertions(+)
>>   create mode 100644 test/py/tests/test_spi.py
>>
> 
> How is this test enabled? Can it run in CI?

If board owner wants to enable it it should be done via uboot-test-hooks repo 
py/travis-ci/* to define exact flash part description to enable this test.
But test is wired already it is just skip if part is not described.

Thanks,
Michal

      reply	other threads:[~2024-07-30  9:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-24 11:06 [PATCH v2] test/py: spi: Add tests for SPI flash device Love Kumar
2024-07-28 19:36 ` Simon Glass
2024-07-30  9:04   ` Michal Simek [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=b68ec280-bd16-4977-af34-3ef8ba59d30e@amd.com \
    --to=michal.simek@amd.com \
    --cc=git@xilinx.com \
    --cc=love.kumar@amd.com \
    --cc=sjg@chromium.org \
    --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