From: "Rob Herring (Arm)" <robh@kernel.org>
To: Zixian Zeng <sycamoremoon376@gmail.com>
Cc: Alexandre Ghiti <alex@ghiti.fr>, Mark Brown <broonie@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
linux-spi@vger.kernel.org, Longbin Li <looong.bin@gmail.com>,
Pratyush Yadav <pratyush@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-riscv@lists.infradead.org,
Conor Dooley <conor.dooley@microchip.com>,
sophgo@lists.linux.dev, Chen Wang <unicorn_wang@outlook.com>,
linux-mtd@lists.infradead.org,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Inochi Amaoto <inochiama@gmail.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Michael Walle <mwalle@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH v4 1/4] spi: dt-bindings: spi-sg2044-nor: Change SOPHGO SG2042
Date: Mon, 21 Jul 2025 10:04:05 -0500 [thread overview]
Message-ID: <175311024481.634831.11395873009603964562.robh@kernel.org> (raw)
In-Reply-To: <20250720-sfg-spifmc-v4-1-033188ad801e@gmail.com>
On Sun, 20 Jul 2025 16:31:43 +0800, Zixian Zeng wrote:
> With further testing, directly using the spi-sg2044-nor driver on SG2042
> does not work. SG2042 is found to lack full compatibility with SG2044.
> SG2044 has OPT register and it's necessary to write but SG2042 does not.
> Due to other possible hardware detail differences, it is better
> to bind SG2042 independently.
>
> Fixes: 8450f1e0d3d0 ("spi: dt-bindings: spi-sg2044-nor: Add SOPHGO SG2042")
> Signed-off-by: Zixian Zeng <sycamoremoon376@gmail.com>
> ---
> Documentation/devicetree/bindings/spi/spi-sg2044-nor.yaml | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-07-21 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-20 8:31 [PATCH v4 0/4] spi: sophgo: Add SPI NOR controller for SG2042 Zixian Zeng
2025-07-20 8:31 ` [PATCH v4 1/4] spi: dt-bindings: spi-sg2044-nor: Change SOPHGO SG2042 Zixian Zeng
2025-07-21 15:04 ` Rob Herring (Arm) [this message]
2025-07-20 8:31 ` [PATCH v4 2/4] spi: spi-sg2044-nor: Add configurable chip_info Zixian Zeng
2025-07-20 8:31 ` [PATCH v4 3/4] spi: spi-sg2044-nor: Add SPI-NOR controller for SG2042 Zixian Zeng
2025-07-20 8:31 ` [PATCH v4 4/4] riscv: dts: sophgo: Add SPI NOR node " Zixian Zeng
2025-07-21 12:58 ` [PATCH v4 0/4] spi: sophgo: Add SPI NOR controller " Chen Wang
2025-07-24 23:34 ` (subset) " Mark Brown
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=175311024481.634831.11395873009603964562.robh@kernel.org \
--to=robh@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=looong.bin@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=sophgo@lists.linux.dev \
--cc=sycamoremoon376@gmail.com \
--cc=tudor.ambarus@linaro.org \
--cc=unicorn_wang@outlook.com \
--cc=vigneshr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox