From: Stephen Boyd <swboyd@chromium.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Karthikeyan Ramasubramanian <kramasub@codeaurora.org>,
Sagar Dharia <sdharia@codeaurora.org>,
Girish Mahadevan <girishm@codeaurora.org>,
Doug Anderson <dianders@chromium.org>
Subject: [PATCH v3 0/3] Fix qcom geni i2c DMA handling
Date: Mon, 24 Sep 2018 16:52:33 -0700 [thread overview]
Message-ID: <20180924235235.182649-1-swboyd@chromium.org> (raw)
(Numbering is weird because I dropped patch 1 but left numbering
the same)
The qcom GENI I2C driver fails DMA sometimes when things
from request firmware are passed in as the message buffer.
This patch series fixes that problem in the first patch
and the second patch cleans up the code a little to reduce
lines and simplify lines.
Cc: Karthikeyan Ramasubramanian <kramasub@codeaurora.org>
Cc: Sagar Dharia <sdharia@codeaurora.org>
Cc: Girish Mahadevan <girishm@codeaurora.org>
Cc: Doug Anderson <dianders@chromium.org>
Changes from v2:
* Dropped first patch because it's applied
* New patch 3 to simplify irq handler
* Updated patch 2 to hoist out common code and remove 'mode'
local variable
Changes from v1:
* Use i2c helpers to map buffers
* New patch 2 to clean up seriously indented code
Stephen Boyd (2):
i2c: i2c-qcom-geni: Simplify tx/rx functions
i2c: i2c-qcom-geni: Simplify irq handler
drivers/i2c/busses/i2c-qcom-geni.c | 149 +++++++++++++----------------
1 file changed, 65 insertions(+), 84 deletions(-)
--
Sent by a computer through tubes
next reply other threads:[~2018-09-24 23:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 23:52 Stephen Boyd [this message]
2018-09-24 23:52 ` [PATCH v3 2/3] i2c: i2c-qcom-geni: Simplify tx/rx functions Stephen Boyd
2018-09-25 21:49 ` Doug Anderson
2018-10-04 7:28 ` alokc
2018-10-11 21:11 ` Wolfram Sang
2018-09-24 23:52 ` [PATCH v3 3/3] i2c: i2c-qcom-geni: Simplify irq handler Stephen Boyd
2018-09-25 21:49 ` Doug Anderson
2018-10-04 7:46 ` alokc
2018-10-11 21:11 ` 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=20180924235235.182649-1-swboyd@chromium.org \
--to=swboyd@chromium.org \
--cc=dianders@chromium.org \
--cc=girishm@codeaurora.org \
--cc=kramasub@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sdharia@codeaurora.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).