From: Jaedon Shin <jaedon.shin@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>,
Kamal Dasu <kdasu.kdev@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-mips@linux-mips.org, Jaedon Shin <jaedon.shin@gmail.com>
Subject: [PATCH 4/9] i2c: brcmstb: enable ACK condition
Date: Wed, 21 Oct 2015 11:36:56 +0900 [thread overview]
Message-ID: <1445395021-4204-5-git-send-email-jaedon.shin@gmail.com> (raw)
In-Reply-To: <1445395021-4204-1-git-send-email-jaedon.shin@gmail.com>
Removes the condition of a message with under 32 bytes in length. The
messages that do not require an ACK are I2C_M_IGNORE_NAK flag.
Signed-off-by: Jaedon Shin <jaedon.shin@gmail.com>
---
drivers/i2c/busses/i2c-brcmstb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-brcmstb.c b/drivers/i2c/busses/i2c-brcmstb.c
index 2d7d155029dc..53eb8b0c9bad 100644
--- a/drivers/i2c/busses/i2c-brcmstb.c
+++ b/drivers/i2c/busses/i2c-brcmstb.c
@@ -330,7 +330,7 @@ static int brcmstb_i2c_xfer_bsc_data(struct brcmstb_i2c_dev *dev,
int no_ack = pmsg->flags & I2C_M_IGNORE_NAK;
/* see if the transaction needs to check NACK conditions */
- if (no_ack || len <= N_DATA_BYTES) {
+ if (no_ack) {
cmd = (pmsg->flags & I2C_M_RD) ? CMD_RD_NOACK
: CMD_WR_NOACK;
pi2creg->ctlhi_reg |= BSC_CTLHI_REG_IGNORE_ACK_MASK;
--
2.6.1
next prev parent reply other threads:[~2015-10-21 2:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 2:36 [PATCH 0/9] i2c: brcmstb: add support for BMIPS_GENERIC Jaedon Shin
2015-10-21 2:36 ` [PATCH 1/9] i2c: brcmstb: make the driver buildable on BMIPS_GENERIC Jaedon Shin
2015-10-22 1:56 ` Florian Fainelli
2015-10-21 2:36 ` [PATCH 3/9] i2c: brcmstb: add missing parenthesis Jaedon Shin
2015-10-22 1:56 ` Florian Fainelli
2015-11-30 15:36 ` Wolfram Sang
2015-10-21 2:36 ` Jaedon Shin [this message]
2015-11-30 15:37 ` [PATCH 4/9] i2c: brcmstb: enable ACK condition Wolfram Sang
[not found] ` <1445395021-4204-1-git-send-email-jaedon.shin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-10-21 2:36 ` [PATCH 2/9] i2c: brcmstb: fix typo in i2c-brcmstb Jaedon Shin
2015-10-22 1:56 ` Florian Fainelli
2015-10-21 2:36 ` [PATCH 5/9] i2c: brcmstb: fix start and stop conditions Jaedon Shin
2015-11-30 15:41 ` Wolfram Sang
2015-10-21 2:36 ` [PATCH 6/9] MIPS: BMIPS: brcmstb: add I2C node for bcm7346 Jaedon Shin
[not found] ` <1445395021-4204-7-git-send-email-jaedon.shin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-10-22 1:57 ` Florian Fainelli
2015-10-21 2:36 ` [PATCH 7/9] MIPS: BMIPS: brcmstb: add I2C node for bcm7358 Jaedon Shin
2015-10-22 1:57 ` Florian Fainelli
2015-10-21 2:37 ` [PATCH 8/9] MIPS: BMIPS: brcmstb: add I2C node for bcm7360 Jaedon Shin
2015-10-22 1:57 ` Florian Fainelli
2015-10-21 2:37 ` [PATCH 9/9] MIPS: BMIPS: brcmstb: add I2C node for bcm7362 Jaedon Shin
2015-10-22 1:57 ` Florian Fainelli
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=1445395021-4204-5-git-send-email-jaedon.shin@gmail.com \
--to=jaedon.shin@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=kdasu.kdev@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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).