[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <cd6360a4247e47cdb819343a05b70d05@AcuMS.aculab.com>
Date: Wed, 30 Jun 2021 16:08:05 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Ulf Hansson' <ulf.hansson@...aro.org>,
Jernej Skrabec <jernej.skrabec@...il.com>
CC: "pizza@...ftnet.org" <pizza@...ftnet.org>,
Arnd Bergmann <arnd@...db.de>,
Kalle Valo <kvalo@...eaurora.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
linux-wireless <linux-wireless@...r.kernel.org>,
netdev <netdev@...r.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: RE: [RFC PATCH] cw1200: use kmalloc() allocation instead of stack
From: Ulf Hansson
> Sent: 30 June 2021 11:03
...
> > It turns out that if CONFIG_VMAP_STACK is enabled and src or dst is
> > memory allocated on stack, SDIO operations fail due to invalid memory
> > address conversion:
...
> > Fix that by using kmalloc() allocated memory for read/write 16/32
> > funtions.
Could a field be added to 'struct cw1200_common'
that the functions could use as a bounce buffer?
ISTM that is DMA are being done there must be some
serialisation in there somewhere that will stop
concurrent accesses.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists