[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20171205110005.00004d66@huawei.com>
Date: Tue, 5 Dec 2017 11:00:05 +0000
From: Jonathan Cameron <Jonathan.Cameron@...wei.com>
To: Mark Brown <broonie@...nel.org>
CC: Wolfram Sang <wsa@...-dreams.de>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
<linux-i2c@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-renesas-soc@...r.kernel.org>, <linux-iio@...r.kernel.org>,
<linux-input@...r.kernel.org>, <linux-media@...r.kernel.org>
Subject: Re: [PATCH v6 0/9] i2c: document DMA handling and add helpers for
it
On Mon, 4 Dec 2017 22:05:41 +0000
Mark Brown <broonie@...nel.org> wrote:
> On Sun, Dec 03, 2017 at 08:43:47PM +0100, Wolfram Sang wrote:
>
> > > It's a bit different in that it's much more likely that a SPI controller
> > > will actually do DMA than an I2C one since the speeds are higher and
> > > there's frequent applications that do large transfers so it's more
> > > likely that people will do the right thing as issues would tend to come
> > > up if they don't.
>
> > Yes, for SPI this is true. I was thinking more of regmap with its
> > usage of different transport mechanisms. But I guess they should all be
> > DMA safe because some of them need to be DMA safe?
>
> Possibly. Hopefully. I guess we'll find out.
>
Yeah, optimistic assumption. Plenty of drivers use regmap for the
convenience of it's caching and field access etc rather than
because they support multiple buses.
I'll audit the IIO drivers and see where we have issues if we
start assuming DMA safe for regmap (which makes sense to me).
Probably worth fixing them all up anyway and tends to be straightforward.
Jonathan
Powered by blists - more mailing lists