From: Iris Chen <irischenlj@fb.com>
Cc: <irischenlj@fb.com>, <pdel@fb.com>, <qemu-devel@nongnu.org>,
<qemu-arm@nongnu.org>, <clg@kaod.org>, <patrick@stwcx.xyz>,
<alistair@alistair23.me>, <kwolf@redhat.com>, <hreitz@redhat.com>,
<peter.maydell@linaro.org>, <andrew@aj.id.au>, <joel@jms.id.au>,
<thuth@redhat.com>, <lvivier@redhat.com>, <pbonzini@redhat.com>,
<qemu-block@nongnu.org>, <dz4list@gmail.com>
Subject: [PATCH 0/2] Add Block Protect (BP) and Top Bottom (TB) bits for write protect
Date: Mon, 27 Jun 2022 11:52:32 -0700 [thread overview]
Message-ID: <20220627185234.1911337-1-irischenlj@fb.com> (raw)
Hey everyone,
Adding the 3 block protection bits and top bottom bits which configure which parts
of the flash are writable and read-only.
These patches are based on previous patches I just submitted:
hw: m25p80: fixing individual test failure when tests are running in isolation
hw: m25p80: add WP# pin and SRWD bit for write protection
hw: m25p80: add tests for write protect (WP# and SRWD bit)
The tests that were added iterates through every different memory protection
case so it takes a little longer to run. Let me know what you think about that
and if that's okay or not.
Thanks,
Iris
Iris Chen (2):
hw: m25p80: Add Block Protect and Top Bottom bits for write protect
hw: m25p80: add tests for BP and TB bit write protect
hw/block/m25p80.c | 74 +++++++++++++++++++----
tests/qtest/aspeed_smc-test.c | 111 ++++++++++++++++++++++++++++++++++
2 files changed, 173 insertions(+), 12 deletions(-)
--
2.30.2
next reply other threads:[~2022-06-27 18:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 18:52 Iris Chen [this message]
2022-06-27 18:52 ` [PATCH 1/2] hw: m25p80: Add Block Protect and Top Bottom bits for write protect Iris Chen
2022-07-01 7:11 ` Cédric Le Goater
2022-07-01 11:40 ` Francisco Iglesias
2022-07-01 12:23 ` Cédric Le Goater
2022-07-01 13:16 ` Francisco Iglesias
2022-07-04 20:50 ` Cédric Le Goater
2022-06-27 18:52 ` [PATCH 2/2] hw: m25p80: add tests for BP and TB bit " Iris Chen
2022-07-01 7:24 ` Cédric Le Goater
2022-07-07 2:16 ` [PATCH v2] hw: m25p80: Add Block Protect and Top Bottom bits for " Iris Chen
2022-07-07 10:36 ` Francisco Iglesias
2022-07-08 16:45 ` [PATCH v3] " Iris Chen
2022-07-08 17:44 ` Francisco Iglesias
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=20220627185234.1911337-1-irischenlj@fb.com \
--to=irischenlj@fb.com \
--cc=alistair@alistair23.me \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=dz4list@gmail.com \
--cc=hreitz@redhat.com \
--cc=joel@jms.id.au \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=patrick@stwcx.xyz \
--cc=pbonzini@redhat.com \
--cc=pdel@fb.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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.