From: Abhishek Sahu <absahu@codeaurora.org>
To: Sricharan R <sricharan@codeaurora.org>
Cc: Andy Gross <andy.gross@linaro.org>,
Wolfram Sang <wsa@the-dreams.de>,
David Brown <david.brown@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 04/12] i2c: qup: schedule EOT and FLUSH tags at the end of transfer
Date: Mon, 19 Feb 2018 16:04:38 +0530 [thread overview]
Message-ID: <1347ec85b53728e3eec771ea78bcbe5f@codeaurora.org> (raw)
In-Reply-To: <dcb7b543-3474-e573-cdc0-010cda5c2d67@codeaurora.org>
On 2018-02-15 20:01, Sricharan R wrote:
> Hi Abhishek,
>
> On 2/3/2018 1:28 PM, Abhishek Sahu wrote:
>> A single BAM transfer can have multiple read and write messages.
>> The EOT and FLUSH tags should be scheduled at the end of BAM HW
>> descriptors. Since the READ and WRITE can be present in any order
>> so for some of the cases, these tags are not being written
>> correctly.
>>
>> Signed-off-by: Abhishek Sahu <absahu@codeaurora.org>
>> ---
>> drivers/i2c/busses/i2c-qup.c | 54
>> ++++++++++++++++++++------------------------
>> 1 file changed, 24 insertions(+), 30 deletions(-)
>>
>> diff --git a/drivers/i2c/busses/i2c-qup.c
>> b/drivers/i2c/busses/i2c-qup.c
>> index bb83a2967..6357aff 100644
>> --- a/drivers/i2c/busses/i2c-qup.c
>> +++ b/drivers/i2c/busses/i2c-qup.c
>> @@ -560,7 +560,7 @@ static int qup_i2c_set_tags_smb(u16 addr, u8
>> *tags, struct qup_i2c_dev *qup,
>> }
>>
>> static int qup_i2c_set_tags(u8 *tags, struct qup_i2c_dev *qup,
>> - struct i2c_msg *msg, int is_dma)
>> + struct i2c_msg *msg)
>> {
>> u16 addr = i2c_8bit_addr_from_msg(msg);
>> int len = 0;
>> @@ -601,11 +601,6 @@ static int qup_i2c_set_tags(u8 *tags, struct
>> qup_i2c_dev *qup,
>> else
>> tags[len++] = data_len;
>>
>> - if ((msg->flags & I2C_M_RD) && last && is_dma) {
>> - tags[len++] = QUP_BAM_INPUT_EOT;
>> - tags[len++] = QUP_BAM_FLUSH_STOP;
>> - }
>> -
>> return len;
>> }
>>
>> @@ -614,7 +609,7 @@ static int qup_i2c_issue_xfer_v2(struct
>> qup_i2c_dev *qup, struct i2c_msg *msg)
>> int data_len = 0, tag_len, index;
>> int ret;
>>
>> - tag_len = qup_i2c_set_tags(qup->blk.tags, qup, msg, 0);
>> + tag_len = qup_i2c_set_tags(qup->blk.tags, qup, msg);
>> index = msg->len - qup->blk.data_len;
>>
>> /* only tags are written for read */
>> @@ -710,7 +705,7 @@ static int qup_i2c_bam_do_xfer(struct qup_i2c_dev
>> *qup, struct i2c_msg *msg,
>> while (qup->blk.pos < blocks) {
>> tlen = (i == (blocks - 1)) ? rem : limit;
>> tags = &qup->start_tag.start[off + len];
>> - len += qup_i2c_set_tags(tags, qup, msg, 1);
>> + len += qup_i2c_set_tags(tags, qup, msg);
>> qup->blk.data_len -= tlen;
>>
>> /* scratch buf to read the start and len tags */
>> @@ -738,17 +733,11 @@ static int qup_i2c_bam_do_xfer(struct
>> qup_i2c_dev *qup, struct i2c_msg *msg,
>> return ret;
>>
>> off += len;
>> - /* scratch buf to read the BAM EOT and FLUSH tags */
>> - ret = qup_sg_set_buf(&qup->brx.sg[rx_buf++],
>> - &qup->brx.tag.start[0],
>> - 2, qup, DMA_FROM_DEVICE);
>> - if (ret)
>> - return ret;
>> } else {
>> while (qup->blk.pos < blocks) {
>> tlen = (i == (blocks - 1)) ? rem : limit;
>> tags = &qup->start_tag.start[off + tx_len];
>> - len = qup_i2c_set_tags(tags, qup, msg, 1);
>> + len = qup_i2c_set_tags(tags, qup, msg);
>> qup->blk.data_len -= tlen;
>>
>> ret = qup_sg_set_buf(&qup->btx.sg[tx_buf++],
>> @@ -768,26 +757,31 @@ static int qup_i2c_bam_do_xfer(struct
>> qup_i2c_dev *qup, struct i2c_msg *msg,
>> }
>> off += tx_len;
>>
>> - if (idx == (num - 1)) {
>> - len = 1;
>> - if (rx_buf) {
>> - qup->btx.tag.start[0] =
>> - QUP_BAM_INPUT_EOT;
>> - len++;
>> - }
>> - qup->btx.tag.start[len - 1] =
>> - QUP_BAM_FLUSH_STOP;
>> - ret = qup_sg_set_buf(&qup->btx.sg[tx_buf++],
>> - &qup->btx.tag.start[0],
>> - len, qup, DMA_TO_DEVICE);
>> - if (ret)
>> - return ret;
>> - }
>> }
>> idx++;
>> msg++;
>> }
>
> While here, can you please split above the if, else in to two
> separate functions ?
> and probably one more function for handling the NACK case down below.
> The function
> size at the moment is too big.
>
Sure. Already I split this function into 2 functions in
[PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum
xfer len
which is making function size smaller. I will check if I can split in
more
functions.
>>
>> + /* schedule the EOT and FLUSH I2C tags */
>> + len = 1;
>> + if (rx_buf) {
>> + qup->btx.tag.start[0] = QUP_BAM_INPUT_EOT;
>> + len++;
>> +
>> + /* scratch buf to read the BAM EOT and FLUSH tags */
>> + ret = qup_sg_set_buf(&qup->brx.sg[rx_buf++],
>> + &qup->brx.tag.start[0],
>> + 2, qup, DMA_FROM_DEVICE);
>> + if (ret)
>> + return ret;
>> + }
>> +
>> + qup->btx.tag.start[len - 1] = QUP_BAM_FLUSH_STOP;
>> + ret = qup_sg_set_buf(&qup->btx.sg[tx_buf++], &qup->btx.tag.start[0],
>> + len, qup, DMA_TO_DEVICE);
>> + if (ret)
>> + return ret;
>> +
>
> May be you can change the commit to make it explicit to say what is
> being
> fixed, like "current code is broken when there is sequence of
> wr,rd,wr" like that.
> Agree on this fix otherwise.
>
Thanks. I will update the commit message to include the failure
case which will give clear idea.
Thanks,
Abhishek
next prev parent reply other threads:[~2018-02-19 10:34 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 7:58 [PATCH 00/12] Major code reorganization to make all i2c transfers working Abhishek Sahu
2018-02-03 7:58 ` [PATCH 01/12] i2c: qup: fixed releasing dma without flush operation completion Abhishek Sahu
2018-02-08 14:03 ` Sricharan R
2018-02-19 10:24 ` Abhishek Sahu
2018-02-27 21:46 ` Christ, Austin
2018-02-27 22:24 ` Andy Gross
2018-02-03 7:58 ` [PATCH 02/12] i2c: qup: minor code reorganization for use_dma Abhishek Sahu
2018-02-27 21:48 ` Christ, Austin
2018-02-27 22:26 ` Andy Gross
2018-02-03 7:58 ` [PATCH 03/12] i2c: qup: remove redundant variables for BAM SG count Abhishek Sahu
2018-02-09 2:16 ` Sricharan R
2018-02-19 10:26 ` Abhishek Sahu
2018-02-27 21:51 ` Christ, Austin
2018-02-27 22:28 ` Andy Gross
2018-02-03 7:58 ` [PATCH 04/12] i2c: qup: schedule EOT and FLUSH tags at the end of transfer Abhishek Sahu
2018-02-15 14:31 ` Sricharan R
2018-02-19 10:34 ` Abhishek Sahu [this message]
2018-02-27 22:36 ` Andy Gross
2018-03-08 13:40 ` Abhishek Sahu
2018-02-03 7:58 ` [PATCH 05/12] i2c: qup: fix the transfer length for BAM rx EOT FLUSH tags Abhishek Sahu
2018-02-27 22:38 ` Andy Gross
2018-02-03 7:58 ` [PATCH 06/12] i2c: qup: proper error handling for i2c error in BAM mode Abhishek Sahu
2018-02-16 4:33 ` Sricharan R
2018-02-27 22:00 ` Christ, Austin
2018-02-27 22:58 ` Andy Gross
2018-03-12 12:34 ` Abhishek Sahu
2018-02-03 7:58 ` [PATCH 07/12] i2c: qup: use the complete transfer length to choose DMA mode Abhishek Sahu
2018-02-16 4:35 ` Sricharan R
2018-02-19 10:49 ` Abhishek Sahu
2018-02-27 22:01 ` Christ, Austin
2018-02-27 22:59 ` Andy Gross
2018-02-03 7:58 ` [PATCH 08/12] i2c: qup: change completion timeout according to transfer length Abhishek Sahu
2018-02-16 4:48 ` Sricharan R
2018-02-19 10:56 ` Abhishek Sahu
2018-02-27 23:05 ` Andy Gross
2018-02-03 7:58 ` [PATCH 09/12] i2c: qup: fix buffer overflow for multiple msg of maximum xfer len Abhishek Sahu
2018-02-16 5:21 ` Sricharan R
2018-02-19 11:24 ` Abhishek Sahu
2018-02-27 22:06 ` Christ, Austin
2018-03-12 13:55 ` Abhishek Sahu
2018-02-27 23:15 ` Andy Gross
2018-03-12 12:28 ` Abhishek Sahu
2018-02-03 7:58 ` [PATCH 10/12] i2c: qup: send NACK for last read sub transfers Abhishek Sahu
2018-02-16 5:39 ` Sricharan R
2018-02-27 22:07 ` Christ, Austin
2018-02-27 23:17 ` Andy Gross
2018-02-03 7:58 ` [PATCH 11/12] i2c: qup: reorganization of driver code to remove polling for qup v1 Abhishek Sahu
2018-02-05 23:03 ` kbuild test robot
2018-02-16 7:44 ` Sricharan R
2018-02-19 13:21 ` Abhishek Sahu
2018-02-20 4:32 ` Sricharan R
2018-02-03 7:58 ` [PATCH 12/12] i2c: qup: reorganization of driver code to remove polling for qup v2 Abhishek Sahu
2018-02-16 11:23 ` Sricharan R
2018-02-19 14:08 ` Abhishek Sahu
2018-02-27 23:24 ` Christ, Austin
2018-03-12 13:58 ` Abhishek Sahu
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=1347ec85b53728e3eec771ea78bcbe5f@codeaurora.org \
--to=absahu@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=sricharan@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).