From: <Takahiro.Kuwano@infineon.com>
To: <festevam@gmail.com>
Cc: <u-boot@0leil.net>, <trini@konsulko.com>, <sjg@chromium.org>,
<kever.yang@rock-chips.com>, <u-boot@lists.u-boot-project.org>,
<festevam@nabladev.com>, <vigneshr@ti.com>
Subject: RE: [PATCH v4 1/4] mtd: spi-nor-ids: Add XMC XM25QH128C
Date: Fri, 31 Jul 2026 03:47:58 +0000 [thread overview]
Message-ID: <455ff3e0fd3446ed9a967db944b91ef6@infineon.com> (raw)
In-Reply-To: <CAOMZO5AUHUEXvM+39N8oybY_W-+cRZAw0BDENGH1e6kB3PTbfw@mail.gmail.com>
> Hi Takahiro-san,
>
> On Wed, Jul 29, 2026 at 5:59 AM <Takahiro.Kuwano@infineon.com> wrote:
>
> > Per the datasheet, this chip supports Dual/Quad ops but for my reference,
> > could you let me know if you tested 1-1-4 or 1-4-4 ops?
>
> I checked the RK3399 SPI1 pin configuration. It only exposes CLK, CS,
> TX/IO0, and RX/IO1; IO2 and IO3 are not muxed to the SPI controller.
> Therefore, my test exercised 1-1-1 operations rather than either 1-1-4 or 1-4-4.
Noted, thank you!
>
> > Anyway,
> > Reviewed-by: Takahiro Kuwano <takahiro.kuwano@infineon.com>
>
> Thanks for the review.
prev parent reply other threads:[~2026-07-31 4:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 19:46 [PATCH v4 1/4] mtd: spi-nor-ids: Add XMC XM25QH128C Fabio Estevam via U-Boot
2026-07-22 19:46 ` [PATCH v4 2/4] rockchip: rk3399: Remove ROC-PC regulator overrides Fabio Estevam via U-Boot
2026-07-22 19:46 ` [PATCH v4 3/4] rockchip: rk3399: Add ROC-PC-PLUS board detection Fabio Estevam via U-Boot
2026-07-23 10:49 ` Quentin Schulz
2026-07-22 19:46 ` [PATCH v4 4/4] rockchip: roc-pc-rk3399: Enable redundant environment Fabio Estevam via U-Boot
2026-07-23 10:50 ` Quentin Schulz
2026-07-29 8:59 ` [PATCH v4 1/4] mtd: spi-nor-ids: Add XMC XM25QH128C Takahiro.Kuwano
2026-07-30 14:26 ` Quentin Schulz via U-Boot
2026-07-31 0:37 ` Fabio Estevam
2026-07-31 3:47 ` Takahiro.Kuwano [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=455ff3e0fd3446ed9a967db944b91ef6@infineon.com \
--to=takahiro.kuwano@infineon.com \
--cc=festevam@gmail.com \
--cc=festevam@nabladev.com \
--cc=kever.yang@rock-chips.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@0leil.net \
--cc=u-boot@lists.u-boot-project.org \
--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 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.