From: Tyrone Ting <warp5tw@gmail.com>
To: avifishman70@gmail.com, tmaimon77@gmail.com,
tali.perry1@gmail.com, venture@google.com, yuenn@google.com,
benjaminfair@google.com, andi.shyti@kernel.org,
andriy.shevchenko@linux.intel.com, wsa@kernel.org,
rand.sec96@gmail.com, wsa+renesas@sang-engineering.com,
warp5tw@gmail.com, tali.perry@nuvoton.com,
Avi.Fishman@nuvoton.com, tomer.maimon@nuvoton.com,
KWLIU@nuvoton.com, JJLIU0@nuvoton.com, kfting@nuvoton.com
Cc: openbmc@lists.ozlabs.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v7 2/4] i2c: npcm: Modify the client address assignment
Date: Mon, 21 Oct 2024 14:27:30 +0800 [thread overview]
Message-ID: <20241021062732.5592-3-kfting@nuvoton.com> (raw)
In-Reply-To: <20241021062732.5592-1-kfting@nuvoton.com>
From: Tyrone Ting <kfting@nuvoton.com>
Store the client address earlier since it might get called in
the i2c_recover_bus() logic flow at the early stage of
npcm_i2c_master_xfer().
Signed-off-by: Tyrone Ting <kfting@nuvoton.com>
Reviewed-by: Tali Perry <tali.perry1@gmail.com>
---
drivers/i2c/busses/i2c-npcm7xx.c | 20 +++++++++++++++++++-
1 file changed, 19 insertions(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-npcm7xx.c b/drivers/i2c/busses/i2c-npcm7xx.c
index c96a25d37c14..a9a9b21f1f0b 100644
--- a/drivers/i2c/busses/i2c-npcm7xx.c
+++ b/drivers/i2c/busses/i2c-npcm7xx.c
@@ -2155,6 +2155,16 @@ static int npcm_i2c_master_xfer(struct i2c_adapter *adap, struct i2c_msg *msgs,
} while (time_is_after_jiffies(time_left) && bus_busy);
+ /*
+ * Previously, the 7-bit address was stored and being converted to
+ * the address of event in the following call to npcm_i2c_master_start_xmit().
+ *
+ * Since there are cases that the i2c_recover_bus() gets called at the
+ * early stage of npcm_i2c_master_xfer(), the address of event is stored
+ * and then used in the i2c_recover_bus().
+ */
+ bus->dest_addr = i2c_8bit_addr_from_msg(msg0);
+
/*
* Check the BER (bus error) state, when ber_state is true, it means that the module
* detects the bus error which is caused by some factor like that the electricity
@@ -2165,6 +2175,15 @@ static int npcm_i2c_master_xfer(struct i2c_adapter *adap, struct i2c_msg *msgs,
* bus is busy.
*/
if (bus_busy || bus->ber_state) {
+ /*
+ * Since the transfer might be a read operation, remove the I2C_M_RD flag
+ * from the bus->dest_addr for the i2c_recover_bus() call later.
+ *
+ * The i2c_recover_bus() uses the address in a write direction to recover
+ * the i2c bus if some error condition occurs.
+ */
+ bus->dest_addr &= ~I2C_M_RD;
+
iowrite8(NPCM_I2CCST_BB, bus->reg + NPCM_I2CCST);
npcm_i2c_reset(bus);
i2c_recover_bus(adap);
@@ -2172,7 +2191,6 @@ static int npcm_i2c_master_xfer(struct i2c_adapter *adap, struct i2c_msg *msgs,
}
npcm_i2c_init_params(bus);
- bus->dest_addr = slave_addr;
bus->msgs = msgs;
bus->msgs_num = num;
bus->cmd_err = 0;
--
2.34.1
next prev parent reply other threads:[~2024-10-21 6:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 6:27 [PATCH v7 0/4] i2c: npcm: read/write operation, checkpatch Tyrone Ting
2024-10-21 6:27 ` [PATCH v7 1/4] i2c: npcm: Modify timeout evaluation mechanism Tyrone Ting
2024-10-21 6:27 ` Tyrone Ting [this message]
2024-10-21 7:01 ` [PATCH v7 2/4] i2c: npcm: Modify the client address assignment Paul Menzel
2024-10-22 8:08 ` Tyrone Ting
2024-10-24 9:28 ` Andi Shyti
2024-10-25 1:36 ` Tyrone Ting
2024-10-24 10:03 ` Andi Shyti
2024-10-25 1:43 ` Tyrone Ting
2024-10-29 8:50 ` Tyrone Ting
2024-11-05 1:52 ` Tyrone Ting
2024-11-19 22:22 ` Andi Shyti
2024-11-21 9:21 ` Tyrone Ting
2024-10-21 6:27 ` [PATCH v7 3/4] i2c: npcm: use i2c frequency table Tyrone Ting
2024-10-24 10:20 ` Andi Shyti
2024-10-25 1:46 ` Tyrone Ting
2024-11-05 1:53 ` Tyrone Ting
2024-11-19 22:25 ` Andi Shyti
2024-11-21 10:11 ` Tali Perry
2024-10-21 6:27 ` [PATCH v7 4/4] i2c: npcm: Enable slave in eob interrupt Tyrone Ting
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=20241021062732.5592-3-kfting@nuvoton.com \
--to=warp5tw@gmail.com \
--cc=Avi.Fishman@nuvoton.com \
--cc=JJLIU0@nuvoton.com \
--cc=KWLIU@nuvoton.com \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=kfting@nuvoton.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=rand.sec96@gmail.com \
--cc=tali.perry1@gmail.com \
--cc=tali.perry@nuvoton.com \
--cc=tmaimon77@gmail.com \
--cc=tomer.maimon@nuvoton.com \
--cc=venture@google.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@kernel.org \
--cc=yuenn@google.com \
/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