From: "Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>
To: Bin Meng <bin.meng@processmission.com>, QEMU <qemu-devel@nongnu.org>
Cc: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>
Subject: Re: [PATCH v2 10/10] docs/devel: Document SSI dummy-cycle ownership
Date: Tue, 7 Jul 2026 15:10:29 +0200 [thread overview]
Message-ID: <8e6e16ff-ceac-4e87-af95-bb52d5cb57f2@oss.qualcomm.com> (raw)
In-Reply-To: <20260707083431.219671-11-bin.meng@processmission.com>
On 7/7/26 10:34, Bin Meng wrote:
> Document the boundary between SPI/SSI controller models and SPI flash
> models when representing fast-read dummy cycles. It explains that
> flash models own command semantics, while controllers own
> hardware-generated dummy transfers and cycle-to-byte conversion.
>
> Signed-off-by: Bin Meng <bin.meng@processmission.com>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@oss.qualcomm.com>
>
> ---
>
> (no changes since v1)
>
> docs/devel/index-internals.rst | 1 +
> docs/devel/ssi.rst | 132 +++++++++++++++++++++++++++++++++
> 2 files changed, 133 insertions(+)
> create mode 100644 docs/devel/ssi.rst
Fails checkpatch.pl, missing:
-- >8 --
diff --git a/MAINTAINERS b/MAINTAINERS
index 1e239f21166..2a9cf15fc7a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2345,2 +2345,3 @@ M: Alistair Francis <alistair@alistair23.me>
S: Maintained
+F: docs/devel/ssi.rst
F: hw/ssi/*
diff --git a/docs/devel/ssi.rst b/docs/devel/ssi.rst
index 864b5d93204..7475d7f241a 100644
--- a/docs/devel/ssi.rst
+++ b/docs/devel/ssi.rst
@@ -1 +1,3 @@
+.. SPDX-License-Identifier: GPL-2.0-or-later
+
================================
---
next prev parent reply other threads:[~2026-07-07 13:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 8:34 [PATCH v2 00/10] hw/{block, ssi}: Fix spi-nor flash dummy byte handling Bin Meng via qemu development
2026-07-07 8:34 ` Bin Meng via
2026-07-07 8:34 ` [PATCH v2 01/10] hw/block: m25p80: Fix dummy byte handling for Winbond flash Bin Meng
2026-07-07 8:34 ` [PATCH v2 02/10] hw/block: m25p80: Fix dummy byte handling for Numonyx/Micron flash Bin Meng
2026-07-07 8:34 ` [PATCH v2 03/10] hw/block: m25p80: Fix dummy byte handling for Macronix flash Bin Meng
2026-07-07 8:34 ` [PATCH v2 04/10] hw/block: m25p80: Fix dummy byte handling for Spansion flash Bin Meng
2026-07-07 12:34 ` Philippe Mathieu-Daudé
2026-07-07 12:51 ` Cédric Le Goater
2026-07-07 14:00 ` Philippe Mathieu-Daudé
2026-07-07 14:05 ` Cédric Le Goater
2026-07-07 14:26 ` Cédric Le Goater
2026-07-07 14:49 ` Bin Meng
2026-07-07 15:05 ` Philippe Mathieu-Daudé
2026-07-07 8:34 ` [PATCH v2 05/10] hw/ssi: npcm7xx_fiu: Correct the dummy cycle emulation logic Bin Meng
2026-07-07 8:34 ` [PATCH v2 06/10] hw/ssi: xilinx_spips: Fix dummy phase handling Bin Meng
2026-07-07 8:34 ` [PATCH v2 07/10] hw/ssi: aspeed_smc: Fix direct-read dummy bytes Bin Meng
2026-07-07 8:34 ` [PATCH v2 08/10] Revert "aspeed/smc: Fix number of dummy cycles for FAST_READ_4 command" Bin Meng
2026-07-07 8:34 ` [PATCH v2 09/10] Revert "aspeed/smc: snoop SPI transfers to fake dummy cycles" Bin Meng
2026-07-07 8:34 ` [PATCH v2 10/10] docs/devel: Document SSI dummy-cycle ownership Bin Meng
2026-07-07 13:10 ` Philippe Mathieu-Daudé [this message]
2026-07-07 9:11 ` [PATCH v2 00/10] hw/{block,ssi}: Fix spi-nor flash dummy byte handling Cédric Le Goater
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=8e6e16ff-ceac-4e87-af95-bb52d5cb57f2@oss.qualcomm.com \
--to=philmd@oss.qualcomm.com \
--cc=bin.meng@processmission.com \
--cc=pierrick.bouvier@oss.qualcomm.com \
--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 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.