From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Wolfram Sang <wsa@the-dreams.de>
Subject: [RFC PATCH 0/4] i2c: document DMA handling and add helper
Date: Tue, 6 Jun 2017 11:20:30 +0200 [thread overview]
Message-ID: <20170606092034.1516-1-wsa+renesas@sang-engineering.com> (raw)
From: Wolfram Sang <wsa@the-dreams.de>
So, after revisiting old mail threads and taking part in a similar discussion
on the USB list, here is an RFC on what I cooked together regarding DMA and I2C
in the Linux world.
I documented my reasoning with patch 2 which mentions a helper function which
gets added with patch 1. Patch 3 shows a super simple example with the
i2c-sh_mobile driver. And patch 4 shows a super complicated example with the
i2c-rcar driver. But it is nice to have such a corner case already in the
beginning of development.
Please let me know what you think. What I surely plan to add until next time is
to fix two central places in the I2C core where the data buffer for block
transfers is currently put on the stack.
A branch can be found here:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/topic/i2c-core-dma
And big kudos to Renesas Electronics for funding this work, thank you very much!
Regards,
Wolfram
Wolfram Sang (4):
i2c: add helper to determine if DMA is favoured
i2c: add docs to clarify DMA handling
i2c: sh_mobile: use helper to decide if DMA is used
i2c: rcar: check for DMA-capable buffers
Documentation/i2c/DMA-considerations | 28 ++++++++++++++++++++++++++++
drivers/i2c/busses/i2c-rcar.c | 18 +++++++++++++-----
drivers/i2c/busses/i2c-sh_mobile.c | 2 +-
include/linux/i2c.h | 29 +++++++++++++++++++++++++++++
4 files changed, 71 insertions(+), 6 deletions(-)
create mode 100644 Documentation/i2c/DMA-considerations
--
2.11.0
next reply other threads:[~2017-06-06 9:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 9:20 Wolfram Sang [this message]
2017-06-06 9:20 ` [RFC PATCH 1/4] i2c: add helper to determine if DMA is favoured Wolfram Sang
2017-06-06 9:20 ` [RFC PATCH 2/4] i2c: add docs to clarify DMA handling Wolfram Sang
2017-06-06 10:03 ` Geert Uytterhoeven
2017-06-06 10:24 ` Wolfram Sang
2017-06-06 10:37 ` Geert Uytterhoeven
2017-06-06 10:54 ` Wolfram Sang
2017-06-06 11:12 ` Geert Uytterhoeven
2017-06-06 11:23 ` Wolfram Sang
2017-06-06 15:29 ` Geert Uytterhoeven
2017-06-06 9:20 ` [RFC PATCH 3/4] i2c: sh_mobile: use helper to decide if DMA is used Wolfram Sang
2017-06-06 9:20 ` [RFC PATCH 4/4] i2c: rcar: check for DMA-capable buffers 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=20170606092034.1516-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).