From: sricharan@codeaurora.org (Sricharan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] i2c: qup: support SMBus block read
Date: Fri, 20 May 2016 14:01:17 +0530 [thread overview]
Message-ID: <000501d1b271$fef3bc90$fcdb35b0$@codeaurora.org> (raw)
In-Reply-To: <757c18e2-562a-9f43-0fb6-ab3e7ac3af88@codeaurora.org>
Hi,
<snip..>
>>> @@ -1128,6 +1173,22 @@ static int qup_i2c_read_one_v2(struct
>>> qup_i2c_dev *qup, struct i2c_msg *msg)
>>> goto err;
>>>
>>> qup->blk.pos++;
>>> +
>>> + /* Handle SMBus block read length */
>>> + if (qup_i2c_check_msg_len(msg) && (msg->len == 1)) {
>>> + if (msg->buf[0] > I2C_SMBUS_BLOCK_MAX) {
>>> + ret = -EPROTO;
>>> + goto err;
>>> + }
>>> + msg->len += msg->buf[0];
>>> + qup->pos = 0;
>>> + qup_i2c_set_read_mode_v2(qup, msg->len);
>>> + qup_i2c_issue_xfer_v2(qup, msg);
>>> + ret = qup_i2c_wait_for_complete(qup, msg);
>>> + if (ret)
>>> + goto err;
>> Is the issue_xfer_v2 needed inside this here ?
>No, qup_i2c_issue_xfer_v2 is needed so that we read rest of the data
>that is indicated by the length we read earlier.
So qup_i2c_issue_xfer_v2 writes the tags and there is one already in the loop above this
check. So if you just do qup_i2c_set_read_mode_v2 and qup_i2c_set_blk_data inside this
check, will not be enough ?
Regards,
Sricharan
next prev parent reply other threads:[~2016-05-20 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1463006736-24652-1-git-send-email-nkaje@codeaurora.org>
[not found] ` <1463006736-24652-2-git-send-email-nkaje@codeaurora.org>
2016-05-18 7:06 ` [PATCH v2 2/2] i2c: qup: support SMBus block read Sricharan
2016-05-19 20:14 ` Naveen Kaje
2016-05-19 20:21 ` Timur Tabi
2016-05-19 21:16 ` Naveen Kaje
2016-05-20 8:31 ` Sricharan [this message]
2016-05-23 17:45 ` Christ, Austin
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='000501d1b271$fef3bc90$fcdb35b0$@codeaurora.org' \
--to=sricharan@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).