From: Pratyush Yadav <pratyush@kernel.org>
To: Santhosh Kumar K <s-k6@ti.com>
Cc: <miquel.raynal@bootlin.com>, <broonie@kernel.org>,
<vigneshr@ti.com>, <marex@denx.de>,
<computersforpeace@gmail.com>, <grmoore@opensource.altera.com>,
<theo.lebrun@bootlin.com>, <linux-spi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <praneeth@ti.com>,
<p-mantena@ti.com>, <a-dutta@ti.com>, <u-kumar1@ti.com>
Subject: Re: [PATCH 4/4] spi: cadence-quadspi: Use BIT() macros where possible
Date: Thu, 04 Sep 2025 16:49:23 +0200 [thread overview]
Message-ID: <mafs0bjnqtgr0.fsf@kernel.org> (raw)
In-Reply-To: <20250904133130.3105736-5-s-k6@ti.com>
On Thu, Sep 04 2025, Santhosh Kumar K wrote:
> From: Vignesh Raghavendra <vigneshr@ti.com>
>
> Convert few open coded bit shifts to BIT() macro for better readability.
> No functional changes intended.
>
> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
> Signed-off-by: Santhosh Kumar K <s-k6@ti.com>
I see there are total 7 hits for the pattern "1 <<". Why not convert
them all while you're at it?
> ---
> drivers/spi/spi-cadence-quadspi.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/spi/spi-cadence-quadspi.c b/drivers/spi/spi-cadence-quadspi.c
> index da3ec15abb3e..b18f095516f2 100644
> --- a/drivers/spi/spi-cadence-quadspi.c
> +++ b/drivers/spi/spi-cadence-quadspi.c
> @@ -335,7 +335,7 @@ static bool cqspi_is_idle(struct cqspi_st *cqspi)
> {
> u32 reg = readl(cqspi->iobase + CQSPI_REG_CONFIG);
>
> - return reg & (1UL << CQSPI_REG_CONFIG_IDLE_LSB);
> + return reg & BIT(CQSPI_REG_CONFIG_IDLE_LSB);
> }
>
> static u32 cqspi_get_rd_sram_level(struct cqspi_st *cqspi)
> @@ -571,7 +571,7 @@ static int cqspi_command_read(struct cqspi_flash_pdata *f_pdata,
> reg |= (dummy_clk & CQSPI_REG_CMDCTRL_DUMMY_MASK)
> << CQSPI_REG_CMDCTRL_DUMMY_LSB;
>
> - reg |= (0x1 << CQSPI_REG_CMDCTRL_RD_EN_LSB);
> + reg |= BIT(CQSPI_REG_CMDCTRL_RD_EN_LSB);
>
> /* 0 means 1 byte. */
> reg |= (((n_rx - 1) & CQSPI_REG_CMDCTRL_RD_BYTES_MASK)
> @@ -1191,7 +1191,7 @@ static void cqspi_chipselect(struct cqspi_flash_pdata *f_pdata)
> * CS2 to 4b'1011
> * CS3 to 4b'0111
> */
> - chip_select = 0xF & ~(1 << chip_select);
> + chip_select = 0xF & ~BIT(chip_select);
> }
>
> reg &= ~(CQSPI_REG_CONFIG_CHIPSELECT_MASK
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2025-09-04 14:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 13:31 [PATCH 0/4] Miscellaneous fixes and clean-ups Santhosh Kumar K
2025-09-04 13:31 ` [PATCH 1/4] spi: cadence-quadspi: Flush posted register writes before INDAC access Santhosh Kumar K
2025-09-04 14:35 ` Pratyush Yadav
2025-09-04 13:31 ` [PATCH 2/4] spi: cadence-quadspi: Flush posted register writes before DAC access Santhosh Kumar K
2025-09-04 14:36 ` Pratyush Yadav
2025-09-04 13:31 ` [PATCH 3/4] spi: cadence-quadspi: Fix cqspi_setup_flash() Santhosh Kumar K
2025-09-04 14:41 ` Pratyush Yadav
2025-09-05 11:04 ` Santhosh Kumar K
2025-09-04 15:32 ` Théo Lebrun
2025-09-05 11:04 ` Santhosh Kumar K
2025-09-04 13:31 ` [PATCH 4/4] spi: cadence-quadspi: Use BIT() macros where possible Santhosh Kumar K
2025-09-04 14:49 ` Pratyush Yadav [this message]
2025-09-05 11:04 ` Santhosh Kumar K
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=mafs0bjnqtgr0.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=a-dutta@ti.com \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=grmoore@opensource.altera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=marex@denx.de \
--cc=miquel.raynal@bootlin.com \
--cc=p-mantena@ti.com \
--cc=praneeth@ti.com \
--cc=s-k6@ti.com \
--cc=theo.lebrun@bootlin.com \
--cc=u-kumar1@ti.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