From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Sanchayan Maity <maitysanchayan@gmail.com>,
linux-input@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
maxime.ripard@free-electrons.com, stefan@agner.ch
Subject: Re: touchscreen: edt-ft5x06: Prevent DMA driver from mapping an area on stack
Date: Sat, 12 Dec 2015 20:42:37 -0800 [thread overview]
Message-ID: <20151213044237.GA22780@dtor-ws> (raw)
In-Reply-To: <20151212171355.GA7362@katana>
On Sat, Dec 12, 2015 at 06:13:55PM +0100, Wolfram Sang wrote:
>
> > Frankly speaking I do not know where the fix should actually be. I2C IMX
> > driver somehow taking care of this or the users of I2C, touchscreen drivers
> > in this case. In my opinion, the fix should be with the touchscreen driver
> > however I did like to have feedback or hear opinions on what is the accepted
> > solution to this.
>
> There is no accepted solution to this yet :( DMA is/was still too rare for
> a serious discussion about this. There is also [1] and probably more...
>
> [1] http://patchwork.ozlabs.org/patch/220137/
I believe vast majority of i2c client drivers do not expect that the
transfer buffer they supply in i2c messages are supposed to be DMAable
(unlike USB and SPI buses that had that requirement from the beginning).
I won't be applying this patch unless we decide that I2C changes the
rules.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2015-12-13 4:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 10:09 [PATCH] touchscreen: edt-ft5x06: Prevent DMA driver from mapping an area on stack Sanchayan Maity
2015-12-12 17:13 ` Wolfram Sang
2015-12-13 4:42 ` Dmitry Torokhov [this message]
2015-12-14 7:53 ` maitysanchayan
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=20151213044237.GA22780@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maitysanchayan@gmail.com \
--cc=maxime.ripard@free-electrons.com \
--cc=stefan@agner.ch \
--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).