From: Greg Ungerer <gerg@linux-m68k.org>
To: Christoph Hellwig <hch@lst.de>, Joakim Zhang <qiangqing.zhang@nxp.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-m68k@lists.linux-m68k.org, uclinux-dev@uclinux.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] net: fec: use dma_alloc_noncoherent for m532x
Date: Thu, 1 Dec 2022 15:41:34 +1000 [thread overview]
Message-ID: <d87264fe-b3e2-39fe-66d2-8201ce81319b@linux-m68k.org> (raw)
In-Reply-To: <20221121095631.216209-2-hch@lst.de>
Hi Christoph,
On 21/11/22 19:56, Christoph Hellwig wrote:
> The m532x coldfire platforms can't properly implement dma_alloc_coherent
> and currently just return noncoherent memory from it. The fec driver
> than works around this with a flush of all caches in the receive path.
> Make this hack a little less bad by using the explicit
> dma_alloc_noncoherent API and documenting the hacky cache flushes.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> drivers/net/ethernet/freescale/fec_main.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/drivers/net/ethernet/freescale/fec_main.c b/drivers/net/ethernet/freescale/fec_main.c
> index 28ef4d3c18789..5230698310b5e 100644
> --- a/drivers/net/ethernet/freescale/fec_main.c
> +++ b/drivers/net/ethernet/freescale/fec_main.c
> @@ -1580,6 +1580,10 @@ fec_enet_rx_queue(struct net_device *ndev, int budget, u16 queue_id)
> struct page *page;
>
> #ifdef CONFIG_M532x
> + /*
> + * Hacky flush of all caches instead of using the DMA API for the TSO
> + * headers.
> + */
> flush_cache_all();
> #endif
> rxq = fep->rx_queue[queue_id];
> @@ -3123,10 +3127,17 @@ static void fec_enet_free_queue(struct net_device *ndev)
> for (i = 0; i < fep->num_tx_queues; i++)
> if (fep->tx_queue[i] && fep->tx_queue[i]->tso_hdrs) {
> txq = fep->tx_queue[i];
> +#ifdef CONFIG_M532x
> dma_free_coherent(&fep->pdev->dev,
> txq->bd.ring_size * TSO_HEADER_SIZE,
> txq->tso_hdrs,
> txq->tso_hdrs_dma);
> +#else
> + dma_free_noncoherent(&fep->pdev->dev,
> + txq->bd.ring_size * TSO_HEADER_SIZE,
> + txq->tso_hdrs, txq->tso_hdrs_dma,
> + DMA_BIDIRECTIONAL);
> +#endif
> }
>
> for (i = 0; i < fep->num_rx_queues; i++)
> @@ -3157,10 +3168,18 @@ static int fec_enet_alloc_queue(struct net_device *ndev)
> txq->tx_wake_threshold =
> (txq->bd.ring_size - txq->tx_stop_threshold) / 2;
>
> +#ifdef CONFIG_M532x
> txq->tso_hdrs = dma_alloc_coherent(&fep->pdev->dev,
> txq->bd.ring_size * TSO_HEADER_SIZE,
> &txq->tso_hdrs_dma,
> GFP_KERNEL);
Even with this corrected this will now end up failing on all other ColdFire types
with the FEC hardware module (all the non-M532x types) once the arch_dma_alloc()
returns NULL.
Did you mean "ifndef CONFIG_COLDFIRE" here?
> +#else
> + /* m68knommu manually flushes all caches in fec_enet_rx_queue */
> + txq->tso_hdrs = dma_alloc_noncoherent(&fep->pdev->dev,
> + txq->bd.ring_size * TSO_HEADER_SIZE,
> + &txq->tso_hdrs_dma, DMA_BIDIRECTIONAL,
> + GFP_KERNEL);
> +#endif
> if (!txq->tso_hdrs) {
> ret = -ENOMEM;
> goto alloc_failed;
And what about the dmam_alloc_coherent() call in fec_enet_init()?
Does that need changing too?
Regards
Greg
next prev parent reply other threads:[~2022-12-01 5:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 9:56 fix dma_alloc_coherent on m68knommu / coldfire Christoph Hellwig
2022-11-21 9:56 ` [PATCH 1/2] net: fec: use dma_alloc_noncoherent for m532x Christoph Hellwig
2022-11-21 10:24 ` Geert Uytterhoeven
2022-11-21 10:43 ` Christoph Hellwig
2022-12-01 5:41 ` Greg Ungerer [this message]
2022-12-02 7:02 ` Christoph Hellwig
2022-12-05 14:09 ` Greg Ungerer
2022-11-21 9:56 ` [PATCH 2/2] m68k: return NULL from dma_alloc_coherent for nommu or coldfire Christoph Hellwig
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=d87264fe-b3e2-39fe-66d2-8201ce81319b@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geert@linux-m68k.org \
--cc=hch@lst.de \
--cc=kuba@kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qiangqing.zhang@nxp.com \
--cc=uclinux-dev@uclinux.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;
as well as URLs for NNTP newsgroup(s).