From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: Hanna Reitz <hreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [PATCH 1/2] hw/pflash: refactor pflash_data_write()
Date: Fri, 5 Jan 2024 15:08:35 +0100 [thread overview]
Message-ID: <eca60f4c-2938-4388-8582-8c8216207201@linaro.org> (raw)
In-Reply-To: <20240105135855.268064-2-kraxel@redhat.com>
On 5/1/24 14:58, Gerd Hoffmann wrote:
> Move the offset calculation, do it once at the start of the function and
> let the 'p' variable point directly to the memory location which should
> be updated. This makes it simpler to update other buffers than
> pfl->storage in an upcoming patch. No functional change.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> hw/block/pflash_cfi01.c | 30 ++++++++++++++++--------------
> 1 file changed, 16 insertions(+), 14 deletions(-)
>
> diff --git a/hw/block/pflash_cfi01.c b/hw/block/pflash_cfi01.c
> index 3e2dc08bd78f..67f1c9773ab3 100644
> --- a/hw/block/pflash_cfi01.c
> +++ b/hw/block/pflash_cfi01.c
> @@ -403,33 +403,35 @@ static void pflash_update(PFlashCFI01 *pfl, int offset,
> static inline void pflash_data_write(PFlashCFI01 *pfl, hwaddr offset,
> uint32_t value, int width, int be)
> {
> - uint8_t *p = pfl->storage;
> + uint8_t *p;
>
> trace_pflash_data_write(pfl->name, offset, width, value, pfl->counter);
> + p = pfl->storage + offset;
> +
> switch (width) {
> case 1:
> - p[offset] = value;
> + p[0] = value;
> break;
> case 2:
> if (be) {
> - p[offset] = value >> 8;
> - p[offset + 1] = value;
> + p[0] = value >> 8;
> + p[1] = value;
> } else {
> - p[offset] = value;
> - p[offset + 1] = value >> 8;
> + p[0] = value;
> + p[1] = value >> 8;
> }
> break;
> case 4:
> if (be) {
> - p[offset] = value >> 24;
> - p[offset + 1] = value >> 16;
> - p[offset + 2] = value >> 8;
> - p[offset + 3] = value;
> + p[0] = value >> 24;
> + p[1] = value >> 16;
> + p[2] = value >> 8;
> + p[3] = value;
> } else {
> - p[offset] = value;
> - p[offset + 1] = value >> 8;
> - p[offset + 2] = value >> 16;
> - p[offset + 3] = value >> 24;
> + p[0] = value;
> + p[1] = value >> 8;
> + p[2] = value >> 16;
> + p[3] = value >> 24;
> }
> break;
> }
Close to commit c3d25271b2 ("hw/block/pflash_cfi02: Use the ldst
API in pflash_write()"):
if (be) {
stn_be_p(p, width, value);
} else {
stn_le_p(p, width, value);
}
next prev parent reply other threads:[~2024-01-05 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 13:58 [PATCH 0/2] hw/pflash: implement update buffer for block writes Gerd Hoffmann
2024-01-05 13:58 ` [PATCH 1/2] hw/pflash: refactor pflash_data_write() Gerd Hoffmann
2024-01-05 14:08 ` Philippe Mathieu-Daudé [this message]
2024-01-05 13:58 ` [PATCH 2/2] hw/pflash: implement update buffer for block writes Gerd Hoffmann
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=eca60f4c-2938-4388-8582-8c8216207201@linaro.org \
--to=philmd@linaro.org \
--cc=hreitz@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).