public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@linux-m68k.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Robin Murphy <robin.murphy@arm.com>,
	iommu@lists.linux.dev,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Wei Fang <wei.fang@nxp.com>, Shenwei Wang <shenwei.wang@nxp.com>,
	Clark Wang <xiaoning.wang@nxp.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	linux-m68k@lists.linux-m68k.org, netdev@vger.kernel.org,
	Jim Quinlan <james.quinlan@broadcom.com>
Subject: Re: [PATCH 5/6] net: fec: use dma_alloc_noncoherent for m532x
Date: Wed, 11 Oct 2023 23:09:07 +1000	[thread overview]
Message-ID: <cff2d9f0-4719-4b88-8ed5-68c8093bcebf@linux-m68k.org> (raw)
In-Reply-To: <20231011055213.GA1131@lst.de>


On 11/10/23 15:52, Christoph Hellwig wrote:
> On Wed, Oct 11, 2023 at 12:20:57AM +1000, Greg Ungerer wrote:
>> That should be M532x.
>>
>> I am pretty sure the code as-is today is broken for the case of using
>> the split cache arrangement (so both instruction and data cache) for any
>> of the version 2 cores too (denoted by the HAVE_CACHE_SPLIT option).
>> But that has probably not been picked up because the default on those
>> has always been instruction cache only.
>>
>> The reason for the special case for the M532x series is that it is a version 3
>> core and they have a unified instruction and data cache. The 523x series is the
>> only version 3 core that Linux supports that has the FEC hardware module.
> 
> So what config option should we check for supporting coherent allocations
> and which not having the hack in fec?
> 
> Here is my guesses based on the above:
> 
> in m68k support coherent allocations with no work if
> 
> CONFIG_COLDIFRE is set and neither CONFIG_CACHE_D or CONFIG_CACHE_BOTH
> is set.

I think this needs to be CONFIG_COLDFIRE is set and none of CONFIG_HAVE_CACHE_CB or
CONFIG_CACHE_D or CONFIG_CACHE_BOTH are set.



> in the fec driver do the alloc_noncoherent and global cache flush
> hack if:
> 
> COMFIG_COLDFIRE && (CONFIG_CACHE_D || CONFIG_CACHE_BOTH)

And then this becomes:

CONFIG_COLDFIRE && (CONFIG_HAVE_CACHE_CB || CONFIG_CACHE_D || CONFIG_CACHE_BOTH)

  reply	other threads:[~2023-10-11 13:09 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09  7:41 fix the non-coherent coldfire dma_alloc_coherent Christoph Hellwig
2023-10-09  7:41 ` [PATCH 1/6] dma-direct: add depdenencies to CONFIG_DMA_GLOBAL_POOL Christoph Hellwig
2023-10-09  8:43   ` Geert Uytterhoeven
2023-10-09  9:16     ` Christoph Hellwig
2023-10-09  9:34       ` Geert Uytterhoeven
2023-10-09  9:43         ` Christoph Hellwig
2023-10-09  9:51           ` Geert Uytterhoeven
2023-10-09 10:04             ` Robin Murphy
2023-10-09 11:10               ` Geert Uytterhoeven
2023-10-09 12:48                 ` Christoph Hellwig
2023-10-09 16:45                   ` Robin Murphy
2023-10-09  7:41 ` [PATCH 2/6] dma-direct: add a CONFIG_ARCH_DMA_ALLOC symbol Christoph Hellwig
2023-10-09  7:41 ` [PATCH 3/6] dma-direct: simplify the use atomic pool logic in dma_direct_alloc Christoph Hellwig
2023-10-09  7:41 ` [PATCH 4/6] dma-direct: warn when coherent allocations aren't supported Christoph Hellwig
2023-10-09  7:41 ` [PATCH 5/6] net: fec: use dma_alloc_noncoherent for m532x Christoph Hellwig
2023-10-09 10:29   ` Robin Murphy
2023-10-09 12:58     ` Christoph Hellwig
2023-10-10 14:44       ` Greg Ungerer
2023-10-16  9:12         ` Geert Uytterhoeven
2023-10-17  8:31           ` Geert Uytterhoeven
2023-10-10 14:20     ` Greg Ungerer
2023-10-11  5:52       ` Christoph Hellwig
2023-10-11 13:09         ` Greg Ungerer [this message]
2023-10-11 18:21           ` Michael Schmitz
2023-10-12 13:25             ` Greg Ungerer
2023-10-12 14:00               ` Christoph Hellwig
2023-10-13  1:48                 ` Greg Ungerer
2023-10-12 19:18               ` Michael Schmitz
2023-10-09  7:41 ` [PATCH 6/6] m68k: don't provide arch_dma_alloc for nommu/coldfire Christoph Hellwig
2023-10-09  8:39 ` fix the non-coherent coldfire dma_alloc_coherent Geert Uytterhoeven
2023-10-09  9:15   ` 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=cff2d9f0-4719-4b88-8ed5-68c8093bcebf@linux-m68k.org \
    --to=gerg@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux.dev \
    --cc=james.quinlan@broadcom.com \
    --cc=linux-imx@nxp.com \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=m.szyprowski@samsung.com \
    --cc=netdev@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=shenwei.wang@nxp.com \
    --cc=wei.fang@nxp.com \
    --cc=xiaoning.wang@nxp.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