From: <Ajay.Kathat@microchip.com>
To: <davidm@egauge.net>
Cc: <Claudiu.Beznea@microchip.com>, <kvalo@codeaurora.org>,
<davem@davemloft.net>, <kuba@kernel.org>,
<linux-wireless@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] wilc1000: Remove misleading USE_SPI_DMA macro
Date: Tue, 7 Dec 2021 12:58:45 +0000 [thread overview]
Message-ID: <bc144dbc-ae56-c763-94f8-c1a5e421e813@microchip.com> (raw)
In-Reply-To: <20211207002453.3193737-1-davidm@egauge.net>
On 07/12/21 05:56, David Mosberger-Tang wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> The USE_SPI_DMA macro name suggests that it could be set to 1 to
> control whether or not SPI DMA should be used. However, that's not
> what it does. If set to 1, it'll set the SPI messages'
> "is_dma_mapped" flag to true, even though the tx/rx buffers aren't
> actually DMA mapped by the driver. In other words, setting this flag
> to 1 will break the driver.
>
> Best to clean up this confusion by removing the macro altogether.
> There is no need to explicitly initialize "is_dma_mapped" because the
> message is cleared to zero anyhow, so "is_dma_mapped" is set to false
> by default.
>
> Signed-off-by: David Mosberger-Tang <davidm@egauge.net>
Thanks!
Acked-by: Ajay Singh <ajay.kathat@microchip.com>
> ---
> drivers/net/wireless/microchip/wilc1000/spi.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/drivers/net/wireless/microchip/wilc1000/spi.c b/drivers/net/wireless/microchip/wilc1000/spi.c
> index 640850f989dd..1856525b9834 100644
> --- a/drivers/net/wireless/microchip/wilc1000/spi.c
> +++ b/drivers/net/wireless/microchip/wilc1000/spi.c
> @@ -99,8 +99,6 @@ static int wilc_spi_reset(struct wilc *wilc);
> #define DATA_PKT_LOG_SZ DATA_PKT_LOG_SZ_MAX
> #define DATA_PKT_SZ (1 << DATA_PKT_LOG_SZ)
>
> -#define USE_SPI_DMA 0
> -
> #define WILC_SPI_COMMAND_STAT_SUCCESS 0
> #define WILC_GET_RESP_HDR_START(h) (((h) >> 4) & 0xf)
>
> @@ -240,7 +238,6 @@ static int wilc_spi_tx(struct wilc *wilc, u8 *b, u32 len)
> memset(&msg, 0, sizeof(msg));
> spi_message_init(&msg);
> msg.spi = spi;
> - msg.is_dma_mapped = USE_SPI_DMA;
> spi_message_add_tail(&tr, &msg);
>
> ret = spi_sync(spi, &msg);
> @@ -284,7 +281,6 @@ static int wilc_spi_rx(struct wilc *wilc, u8 *rb, u32 rlen)
> memset(&msg, 0, sizeof(msg));
> spi_message_init(&msg);
> msg.spi = spi;
> - msg.is_dma_mapped = USE_SPI_DMA;
> spi_message_add_tail(&tr, &msg);
>
> ret = spi_sync(spi, &msg);
> @@ -323,7 +319,6 @@ static int wilc_spi_tx_rx(struct wilc *wilc, u8 *wb, u8 *rb, u32 rlen)
> memset(&msg, 0, sizeof(msg));
> spi_message_init(&msg);
> msg.spi = spi;
> - msg.is_dma_mapped = USE_SPI_DMA;
>
> spi_message_add_tail(&tr, &msg);
> ret = spi_sync(spi, &msg);
> --
> 2.25.1
>
next prev parent reply other threads:[~2021-12-07 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 0:26 [PATCH] wilc1000: Remove misleading USE_SPI_DMA macro David Mosberger-Tang
2021-12-07 12:58 ` Ajay.Kathat [this message]
2021-12-14 18:44 ` Kalle Valo
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=bc144dbc-ae56-c763-94f8-c1a5e421e813@microchip.com \
--to=ajay.kathat@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=davidm@egauge.net \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox