From: Wolfram Sang <wsa@the-dreams.de>
To: Sanchayan Maity <maitysanchayan@gmail.com>
Cc: linux-input@vger.kernel.org, linux-i2c@vger.kernel.org,
dmitry.torokhov@gmail.com, 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 18:13:55 +0100 [thread overview]
Message-ID: <20151212171355.GA7362@katana> (raw)
In-Reply-To: <e0311a5e79a315814e8678c9ef4a32563c01d1e0.1449913392.git.maitysanchayan@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
> 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/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: touchscreen: edt-ft5x06: Prevent DMA driver from mapping an area on stack
Date: Sat, 12 Dec 2015 18:13:55 +0100 [thread overview]
Message-ID: <20151212171355.GA7362@katana> (raw)
In-Reply-To: <e0311a5e79a315814e8678c9ef4a32563c01d1e0.1449913392.git.maitysanchayan@gmail.com>
> 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/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151212/cc0d487a/attachment.sig>
next prev parent reply other threads:[~2015-12-12 17:14 UTC|newest]
Thread overview: 8+ 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 10:09 ` Sanchayan Maity
2015-12-12 17:13 ` Wolfram Sang [this message]
2015-12-12 17:13 ` Wolfram Sang
2015-12-13 4:42 ` Dmitry Torokhov
2015-12-13 4:42 ` Dmitry Torokhov
2015-12-14 7:53 ` maitysanchayan
2015-12-14 7:53 ` maitysanchayan at gmail.com
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=20151212171355.GA7362@katana \
--to=wsa@the-dreams.de \
--cc=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 \
/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 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.