[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <X+IQRct0Zsm87H4+@kroah.com>
Date: Tue, 22 Dec 2020 16:27:01 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Kalle Valo <kvalo@...eaurora.org>
Cc: Jerome Pouiller <Jerome.Pouiller@...abs.com>,
devel@...verdev.osuosl.org, devicetree@...r.kernel.org,
Ulf Hansson <ulf.hansson@...aro.org>, netdev@...r.kernel.org,
linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>, linux-mmc@...r.kernel.org,
Pali Rohár <pali@...nel.org>,
"David S . Miller" <davem@...emloft.net>
Subject: Re: [PATCH v3 09/24] wfx: add hwio.c/hwio.h
On Tue, Dec 22, 2020 at 05:10:11PM +0200, Kalle Valo wrote:
> Jerome Pouiller <Jerome.Pouiller@...abs.com> writes:
>
> > +/*
> > + * Internal helpers.
> > + *
> > + * About CONFIG_VMAP_STACK:
> > + * When CONFIG_VMAP_STACK is enabled, it is not possible to run DMA on stack
> > + * allocated data. Functions below that work with registers (aka functions
> > + * ending with "32") automatically reallocate buffers with kmalloc. However,
> > + * functions that work with arbitrary length buffers let's caller to handle
> > + * memory location. In doubt, enable CONFIG_DEBUG_SG to detect badly located
> > + * buffer.
> > + */
>
> This sounds very hacky to me, I have understood that you should never
> use stack with DMA.
You should never do that because some platforms do not support it, so no
driver should ever try to do that as they do not know what platform they
are running on.
thanks,
greg k-h
Powered by blists - more mailing lists