From: Mark Brown <broonie@kernel.org> To: Wolfram Sang <wsa@the-dreams.de> Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>, linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org, linux-iio@vger.kernel.org, linux-input@vger.kernel.org, linux-media@vger.kernel.org Subject: Re: [PATCH v6 0/9] i2c: document DMA handling and add helpers for it Date: Mon, 4 Dec 2017 22:05:41 +0000 [thread overview] Message-ID: <20171204220541.GA11658@finisterre> (raw) In-Reply-To: <20171203194347.bbds47a72xbc4nvl@ninjato> [-- Attachment #1: Type: text/plain, Size: 626 bytes --] 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. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> To: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org> Cc: Wolfram Sang <wsa+renesas-jBu1N2QxHDJrcw3mvpCnnVaTQe2KTcn/@public.gmane.org>, linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Subject: Re: [PATCH v6 0/9] i2c: document DMA handling and add helpers for it Date: Mon, 4 Dec 2017 22:05:41 +0000 [thread overview] Message-ID: <20171204220541.GA11658@finisterre> (raw) In-Reply-To: <20171203194347.bbds47a72xbc4nvl@ninjato> [-- Attachment #1: Type: text/plain, Size: 626 bytes --] 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. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-12-04 22:05 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-04 20:20 [PATCH v6 0/9] i2c: document DMA handling and add helpers for it Wolfram Sang 2017-11-04 20:20 ` Wolfram Sang 2017-11-04 20:20 ` [PATCH v6 1/9] i2c: add a message flag for DMA safe buffers Wolfram Sang 2017-11-04 20:20 ` [PATCH v6 2/9] i2c: add helpers to ease DMA handling Wolfram Sang 2017-11-04 20:20 ` Wolfram Sang 2017-11-04 20:20 ` [PATCH v6 3/9] i2c: dev: mark RDWR buffers as DMA_SAFE Wolfram Sang 2017-11-04 20:20 ` Wolfram Sang 2017-11-04 20:20 ` [PATCH v6 4/9] i2c: refactor i2c_master_{send_recv} Wolfram Sang 2017-11-11 0:03 ` Jonathan Cameron 2017-11-11 0:03 ` Jonathan Cameron 2017-11-04 20:20 ` [PATCH v6 5/9] i2c: add i2c_master_{send|recv}_dmasafe Wolfram Sang 2017-11-11 0:08 ` Jonathan Cameron 2017-11-11 0:08 ` Jonathan Cameron 2017-11-04 20:20 ` [PATCH v6 6/9] i2c: smbus: use DMA safe buffers for emulated SMBus transactions Wolfram Sang 2017-11-11 0:13 ` Jonathan Cameron 2017-11-11 0:13 ` Jonathan Cameron 2017-11-04 20:20 ` [PATCH v6 7/9] i2c: add docs to clarify DMA handling Wolfram Sang 2017-11-04 20:20 ` [PATCH v6 8/9] i2c: sh_mobile: use core helper to decide when to use DMA Wolfram Sang 2017-11-04 20:20 ` [PATCH v6 9/9] i2c: rcar: skip DMA if buffer is not safe Wolfram Sang 2017-11-08 22:50 ` [PATCH v6 0/9] i2c: document DMA handling and add helpers for it Mark Brown 2017-11-27 18:51 ` Wolfram Sang 2017-11-28 15:34 ` Mark Brown 2017-12-03 19:43 ` Wolfram Sang 2017-12-04 22:05 ` Mark Brown [this message] 2017-12-04 22:05 ` Mark Brown 2017-12-05 11:00 ` Jonathan Cameron 2017-12-05 11:00 ` Jonathan Cameron 2017-12-04 21:25 ` Wolfram Sang
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=20171204220541.GA11658@finisterre \ --to=broonie@kernel.org \ --cc=linux-i2c@vger.kernel.org \ --cc=linux-iio@vger.kernel.org \ --cc=linux-input@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-media@vger.kernel.org \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=wsa+renesas@sang-engineering.com \ --cc=wsa@the-dreams.de \ /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: linkBe 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.