From: valentin.longchamp@keymile.com (Valentin Longchamp)
To: linux-arm-kernel@lists.infradead.org
Subject: dma_alloc_coherent and cache?
Date: Thu, 17 Apr 2014 16:35:00 +0200 [thread overview]
Message-ID: <534FE694.8090102@keymile.com> (raw)
In-Reply-To: <20140415081004.GJ22546@lunn.ch>
On 04/15/2014 10:10 AM, Andrew Lunn wrote:
> On Tue, Apr 15, 2014 at 09:43:38AM +0400, Lee Essen wrote:
>> Hi,
>>
>> I'm working on a driver for a Marvell switch device (98dx4122) where the basic interface closely resembles the mv643xx_eth device.
>
> There is basic support for this SoC in the kernel. See
> arch/arm/boot/dts/kirkwood-98dx4122.dtsi and
> arch/arm/boot/dts/kirkwood-km_kirkwood.dts which is keymile's
> reference design.
>
> Keymile are the experts for this device within the kernel community,
> so maybe they can comment?
>
Hi Lee and Andrew,
Sorry for the quite late answer. At Keymile we rely on the driver (CPSS) Marvell
provides to manage the switch but personally I am not very happy about this
situation and I think your effort is great.
As you know, there are several ways to access the Switch from the CPU, one of
them is through the "internal" RGMII that you use, and another one is through
the CPU internal bus that we use at Keymile (thus we have to reserve a Mbus
window for the switch that then can be ioremapped). Since I have never used the
RGMII device, I cannot really give you some interesting hints here.
If we are talking about feroceon and caches, we have experienced a lot of
problems with the L2 cache that was sometimes not coherent with the CPU, but
with the latest versions of u-boot and Linux we do not see that anymore, so I
don't think you problem is this one.
That's unfortunately all the information I can provide to this thread.
Valentin
next prev parent reply other threads:[~2014-04-17 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 5:43 dma_alloc_coherent and cache? Lee Essen
2014-04-15 8:10 ` Andrew Lunn
2014-04-17 14:35 ` Valentin Longchamp [this message]
2014-04-15 8:43 ` Arnd Bergmann
2014-04-15 10:01 ` Lee Essen
2014-04-15 10:49 ` Arnd Bergmann
2014-04-15 16:22 ` Lee Essen
2014-04-15 16:49 ` Andrew Lunn
2014-04-15 21:54 ` Troy Kisky
2014-04-16 15:55 ` Lee Essen
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=534FE694.8090102@keymile.com \
--to=valentin.longchamp@keymile.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.