From: Frank Li <Frank.li@nxp.com>
To: Hans Zhang <18255117159@163.com>
Cc: broonie@kernel.org, sunny.luo@amlogic.com,
xianwei.zhao@amlogic.com, neil.armstrong@linaro.org,
khilman@baylibre.com, han.xu@nxp.com, haibo.chen@nxp.com,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
lhjeff911@gmail.com, hayashi.kunihiko@socionext.com,
mhiramat@kernel.org, jbrunet@baylibre.com,
martin.blumenstingl@googlemail.com, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH 05/10] spi: nxp-xspi: Use FIELD_MODIFY()
Date: Tue, 5 May 2026 11:39:52 -0400 [thread overview]
Message-ID: <afoPSF5g3WVHJk0L@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20260430155456.36998-6-18255117159@163.com>
On Thu, Apr 30, 2026 at 11:54:51PM +0800, Hans Zhang wrote:
> Use FIELD_MODIFY() to remove open-coded bit manipulation.
> No functional change intended.
>
> Signed-off-by: Hans Zhang <18255117159@163.com>
> ---
Reviewed-by: Frank Li <Frank.Li@nxp.com>
> drivers/spi/spi-nxp-xspi.c | 12 ++++--------
> 1 file changed, 4 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/spi/spi-nxp-xspi.c b/drivers/spi/spi-nxp-xspi.c
> index 385302a6e62f..037eac24e6fd 100644
> --- a/drivers/spi/spi-nxp-xspi.c
> +++ b/drivers/spi/spi-nxp-xspi.c
> @@ -493,9 +493,8 @@ static void nxp_xspi_disable_ddr(struct nxp_xspi *xspi)
> writel(reg, base + XSPI_MCR);
>
> reg &= ~XSPI_MCR_DDR_EN;
> - reg &= ~XSPI_MCR_DQS_FA_SEL_MASK;
> /* Use dummy pad loopback mode to sample data */
> - reg |= FIELD_PREP(XSPI_MCR_DQS_FA_SEL_MASK, 0x01);
> + FIELD_MODIFY(XSPI_MCR_DQS_FA_SEL_MASK, ®, 0x01);
> writel(reg, base + XSPI_MCR);
> xspi->support_max_rate = 133000000;
>
> @@ -524,15 +523,13 @@ static void nxp_xspi_enable_ddr(struct nxp_xspi *xspi)
> writel(reg, base + XSPI_MCR);
>
> reg |= XSPI_MCR_DDR_EN;
> - reg &= ~XSPI_MCR_DQS_FA_SEL_MASK;
> /* Use external dqs to sample data */
> - reg |= FIELD_PREP(XSPI_MCR_DQS_FA_SEL_MASK, 0x03);
> + FIELD_MODIFY(XSPI_MCR_DQS_FA_SEL_MASK, ®, 0x03);
> writel(reg, base + XSPI_MCR);
> xspi->support_max_rate = 200000000;
>
> reg = readl(base + XSPI_FLSHCR);
> - reg &= ~XSPI_FLSHCR_TDH_MASK;
> - reg |= FIELD_PREP(XSPI_FLSHCR_TDH_MASK, 0x01);
> + FIELD_MODIFY(XSPI_FLSHCR_TDH_MASK, ®, 0x01);
> writel(reg, base + XSPI_FLSHCR);
>
> reg = FIELD_PREP(XSPI_SMPR_DLLFSMPFA_MASK, 0x04);
> @@ -1096,8 +1093,7 @@ static int nxp_xspi_default_setup(struct nxp_xspi *xspi)
>
> /* Give read/write access right to EENV0 */
> reg = readl(base + XSPI_FRAD0_WORD2);
> - reg &= ~XSPI_FRAD0_WORD2_MD0ACP_MASK;
> - reg |= FIELD_PREP(XSPI_FRAD0_WORD2_MD0ACP_MASK, 0x03);
> + FIELD_MODIFY(XSPI_FRAD0_WORD2_MD0ACP_MASK, ®, 0x03);
> writel(reg, base + XSPI_FRAD0_WORD2);
>
> /* Enable the FRAD check for EENV0 */
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-05-05 15:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 15:54 [PATCH 00/10] spi: Use FIELD_MODIFY() for bitfield operations Hans Zhang
2026-04-30 15:54 ` [PATCH 01/10] spi: amlogic-spifc-a1: Use FIELD_MODIFY() Hans Zhang
2026-04-30 15:54 ` [PATCH 02/10] spi: amlogic-spisg: " Hans Zhang
2026-04-30 15:54 ` [PATCH 03/10] spi: cadence-xspi: " Hans Zhang
2026-05-01 0:52 ` Mark Brown
2026-04-30 15:54 ` [PATCH 04/10] spi: meson-spicc: " Hans Zhang
2026-04-30 15:54 ` [PATCH 05/10] spi: nxp-xspi: " Hans Zhang
2026-05-05 15:39 ` Frank Li [this message]
2026-04-30 15:54 ` [PATCH 06/10] spi: sn-f-ospi: " Hans Zhang
2026-04-30 15:54 ` [PATCH 07/10] spi: stm32-ospi: " Hans Zhang
2026-04-30 15:54 ` [PATCH 08/10] spi: stm32-qspi: " Hans Zhang
2026-04-30 15:54 ` [PATCH 09/10] spi: sunplus-sp7021: " Hans Zhang
2026-04-30 15:54 ` [PATCH 10/10] spi: uniphier: " Hans Zhang
2026-05-01 8:30 ` [PATCH 00/10] spi: Use FIELD_MODIFY() for bitfield operations David Laight
2026-05-05 4:23 ` Hans Zhang
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=afoPSF5g3WVHJk0L@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=18255117159@163.com \
--cc=alexandre.torgue@foss.st.com \
--cc=broonie@kernel.org \
--cc=haibo.chen@nxp.com \
--cc=han.xu@nxp.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=imx@lists.linux.dev \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=lhjeff911@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mhiramat@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=sunny.luo@amlogic.com \
--cc=xianwei.zhao@amlogic.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