[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141209102904.GJ11285@n2100.arm.linux.org.uk>
Date: Tue, 9 Dec 2014 10:29:05 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Arend van Spriel <arend@...adcom.com>
Cc: Catalin Marinas <catalin.marinas@....com>,
Arnd Bergmann <arnd@...db.de>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
brcm80211-dev-list <brcm80211-dev-list@...adcom.com>,
linux-wireless <linux-wireless@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Will Deacon <Will.Deacon@....com>,
Hante Meuleman <meuleman@...adcom.com>,
"hauke@...ke-m.de" <hauke@...ke-m.de>,
David Miller <davem@...emloft.net>,
Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: using DMA-API on ARM
On Tue, Dec 09, 2014 at 11:19:40AM +0100, Arend van Spriel wrote:
> The issue did not trigger overnight so it seems setting bit 22 <Shared
> Attribute _Override_ Enable> solves the issue over here. Now the question is
> how to move forward with this. As I understood from Catalin this patch was
> not included as it was not considered responsibility of the linux kernel.
It is preferable for firmware to configure the L2 cache appropriately,
which includes things like the prefetch offsets as well as feature bits
like bit 22.
I think what I'll do is queue up a patch which adds a warning if bit 22
is not set, suggesting that firmware is updated to set this bit.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists