Message ID | 20230904231439.485925-1-aryan.srivastava@alliedtelesis.co.nz |
---|---|
State | Superseded |
Headers | show |
Series | i2c:octeon:Add block-mode r/w | expand |
Hi Aryan, kernel test robot noticed the following build errors: [auto build test ERROR on wsa/i2c/for-next] [also build test ERROR on linus/master v6.5 next-20230831] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Aryan-Srivastava/i2c-octeon-Add-block-mode-r-w/20230905-071739 base: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-next patch link: https://lore.kernel.org/r/20230904231439.485925-1-aryan.srivastava%40alliedtelesis.co.nz patch subject: [PATCH] i2c:octeon:Add block-mode r/w config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20230905/202309051413.SkL3myiV-lkp@intel.com/config) compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230905/202309051413.SkL3myiV-lkp@intel.com/reproduce) If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags | Reported-by: kernel test robot <lkp@intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202309051413.SkL3myiV-lkp@intel.com/ All errors (new ones prefixed by >>): drivers/i2c/busses/i2c-octeon-core.c: In function 'octeon_i2c_hlc_block_comp_write': >> drivers/i2c/busses/i2c-octeon-core.c:725:17: error: label 'ret' used but not defined 725 | goto ret; | ^~~~ vim +/ret +725 drivers/i2c/busses/i2c-octeon-core.c 674 675 /* high-level-controller composite block write+write, m[0]len<=2, m[1]len<=1024 */ 676 static int octeon_i2c_hlc_block_comp_write(struct octeon_i2c *i2c, struct i2c_msg *msgs) 677 { 678 bool set_ext = false; 679 int i, j, len, ret = 0; 680 u64 cmd, buf = 0, ext = 0; 681 682 octeon_i2c_hlc_enable(i2c); 683 octeon_i2c_block_enable(i2c); 684 685 /* Write (size - 1) into block control register */ 686 len = msgs[1].len - 1; 687 octeon_i2c_writeq_flush((u64)(len), i2c->twsi_base + TWSI_BLOCK_CTL(i2c)); 688 689 /* Prepare core command */ 690 cmd = SW_TWSI_V | SW_TWSI_SOVR; 691 cmd |= (u64)(msgs[0].addr & 0x7full) << SW_TWSI_ADDR_SHIFT; 692 693 if (msgs[0].flags & I2C_M_TEN) 694 cmd |= SW_TWSI_OP_10_IA; 695 else 696 cmd |= SW_TWSI_OP_7_IA; 697 698 if (msgs[0].len == 2) { 699 cmd |= SW_TWSI_EIA; 700 ext |= (u64)msgs[0].buf[0] << SW_TWSI_IA_SHIFT; 701 set_ext = true; 702 cmd |= (u64)msgs[0].buf[1] << SW_TWSI_IA_SHIFT; 703 } else { 704 cmd |= (u64)msgs[0].buf[0] << SW_TWSI_IA_SHIFT; 705 } 706 707 /* Write msg into FIFO buffer */ 708 octeon_i2c_writeq_flush(TWSI_BLOCK_STS_RESET_PTR, i2c->twsi_base + TWSI_BLOCK_STS(i2c)); 709 for (i = 0; i < len; i += 8) { 710 buf = 0; 711 for (j = 7; j >= 0; j--) 712 buf |= (msgs[1].buf[i + (7 - j)] << (8 * j)); 713 octeon_i2c_writeq_flush(buf, i2c->twsi_base + TWSI_BLOCK_FIFO(i2c)); 714 } 715 if (set_ext) 716 octeon_i2c_writeq_flush(ext, i2c->twsi_base + SW_TWSI_EXT(i2c)); 717 718 /* Send command to core (send data in FIFO) */ 719 octeon_i2c_hlc_int_clear(i2c); 720 octeon_i2c_writeq_flush(cmd, i2c->twsi_base + SW_TWSI(i2c)); 721 722 /* Wait for transaction to complete */ 723 ret = octeon_i2c_hlc_wait(i2c); 724 if (ret) > 725 goto ret; 726 727 cmd = __raw_readq(i2c->twsi_base + SW_TWSI(i2c)); 728 if ((cmd & SW_TWSI_R) == 0) 729 return octeon_i2c_check_status(i2c, false); 730 731 octeon_i2c_block_disable(i2c); 732 return ret; 733 } 734
Hi Aryan, kernel test robot noticed the following build errors: [auto build test ERROR on wsa/i2c/for-next] [also build test ERROR on linus/master v6.5 next-20230905] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Aryan-Srivastava/i2c-octeon-Add-block-mode-r-w/20230905-071739 base: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-next patch link: https://lore.kernel.org/r/20230904231439.485925-1-aryan.srivastava%40alliedtelesis.co.nz patch subject: [PATCH] i2c:octeon:Add block-mode r/w config: riscv-randconfig-001-20230905 (https://download.01.org/0day-ci/archive/20230905/202309051505.K5sogLFe-lkp@intel.com/config) compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230905/202309051505.K5sogLFe-lkp@intel.com/reproduce) If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags | Reported-by: kernel test robot <lkp@intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202309051505.K5sogLFe-lkp@intel.com/ All errors (new ones prefixed by >>): >> drivers/i2c/busses/i2c-octeon-core.c:725:8: error: use of undeclared label 'ret' 725 | goto ret; | ^ 1 error generated. vim +/ret +725 drivers/i2c/busses/i2c-octeon-core.c 674 675 /* high-level-controller composite block write+write, m[0]len<=2, m[1]len<=1024 */ 676 static int octeon_i2c_hlc_block_comp_write(struct octeon_i2c *i2c, struct i2c_msg *msgs) 677 { 678 bool set_ext = false; 679 int i, j, len, ret = 0; 680 u64 cmd, buf = 0, ext = 0; 681 682 octeon_i2c_hlc_enable(i2c); 683 octeon_i2c_block_enable(i2c); 684 685 /* Write (size - 1) into block control register */ 686 len = msgs[1].len - 1; 687 octeon_i2c_writeq_flush((u64)(len), i2c->twsi_base + TWSI_BLOCK_CTL(i2c)); 688 689 /* Prepare core command */ 690 cmd = SW_TWSI_V | SW_TWSI_SOVR; 691 cmd |= (u64)(msgs[0].addr & 0x7full) << SW_TWSI_ADDR_SHIFT; 692 693 if (msgs[0].flags & I2C_M_TEN) 694 cmd |= SW_TWSI_OP_10_IA; 695 else 696 cmd |= SW_TWSI_OP_7_IA; 697 698 if (msgs[0].len == 2) { 699 cmd |= SW_TWSI_EIA; 700 ext |= (u64)msgs[0].buf[0] << SW_TWSI_IA_SHIFT; 701 set_ext = true; 702 cmd |= (u64)msgs[0].buf[1] << SW_TWSI_IA_SHIFT; 703 } else { 704 cmd |= (u64)msgs[0].buf[0] << SW_TWSI_IA_SHIFT; 705 } 706 707 /* Write msg into FIFO buffer */ 708 octeon_i2c_writeq_flush(TWSI_BLOCK_STS_RESET_PTR, i2c->twsi_base + TWSI_BLOCK_STS(i2c)); 709 for (i = 0; i < len; i += 8) { 710 buf = 0; 711 for (j = 7; j >= 0; j--) 712 buf |= (msgs[1].buf[i + (7 - j)] << (8 * j)); 713 octeon_i2c_writeq_flush(buf, i2c->twsi_base + TWSI_BLOCK_FIFO(i2c)); 714 } 715 if (set_ext) 716 octeon_i2c_writeq_flush(ext, i2c->twsi_base + SW_TWSI_EXT(i2c)); 717 718 /* Send command to core (send data in FIFO) */ 719 octeon_i2c_hlc_int_clear(i2c); 720 octeon_i2c_writeq_flush(cmd, i2c->twsi_base + SW_TWSI(i2c)); 721 722 /* Wait for transaction to complete */ 723 ret = octeon_i2c_hlc_wait(i2c); 724 if (ret) > 725 goto ret; 726 727 cmd = __raw_readq(i2c->twsi_base + SW_TWSI(i2c)); 728 if ((cmd & SW_TWSI_R) == 0) 729 return octeon_i2c_check_status(i2c, false); 730 731 octeon_i2c_block_disable(i2c); 732 return ret; 733 } 734
Hi Aryan, In the title, please leave a space after the ':' i2c: octeon: Add block-mode r/w Please check with "git log drivers..." to see what's the rule in a particular community. I guess Wolfram can fix this, though, before pushing. [...] > +/* high-level-controller composite block write+read, msg0=addr, msg1=data */ I think this comment is fine and great to have it, but it's missing a bit of clarity, can you please expand the concept? > +static int octeon_i2c_hlc_block_comp_read(struct octeon_i2c *i2c, struct i2c_msg *msgs) > +{ > + int i, j, len, ret = 0; > + u64 cmd = 0, rd = 0; can please you move rd, j inside the for loop? The basic common sense is to have all variable declared in the innermost section in order to avoid confusion. It's a nitpick though, not a strong comment and, afaik, not a real rule. Same comment for the function below. > + > + octeon_i2c_hlc_enable(i2c); > + octeon_i2c_block_enable(i2c); > + > + /* Write (size - 1) into block control register */ > + len = msgs[1].len - 1; > + octeon_i2c_writeq_flush((u64)(len), i2c->twsi_base + TWSI_BLOCK_CTL(i2c)); > + > + /* Prepare core command */ > + cmd = SW_TWSI_V | SW_TWSI_R | SW_TWSI_SOVR; > + cmd |= (u64)(msgs[0].addr & 0x7full) << SW_TWSI_ADDR_SHIFT; > + > + if (msgs[0].flags & I2C_M_TEN) > + cmd |= SW_TWSI_OP_10_IA; > + else > + cmd |= SW_TWSI_OP_7_IA; > + > + if (msgs[0].len == 2) { > + u64 ext = 0; > + > + cmd |= SW_TWSI_EIA; > + ext = (u64)msgs[0].buf[0] << SW_TWSI_IA_SHIFT; > + cmd |= (u64)msgs[0].buf[1] << SW_TWSI_IA_SHIFT; > + octeon_i2c_writeq_flush(ext, i2c->twsi_base + SW_TWSI_EXT(i2c)); > + } else { > + cmd |= (u64)msgs[0].buf[0] << SW_TWSI_IA_SHIFT; > + } This first part is basically a copy/paste with the write() function... can we put them together in a common function? Can we put as much as we can in a single function? > + /* Send command to core (send data to FIFO) */ > + octeon_i2c_hlc_int_clear(i2c); > + octeon_i2c_writeq_flush(cmd, i2c->twsi_base + SW_TWSI(i2c)); > + > + /* Wait for transaction to complete */ > + ret = octeon_i2c_hlc_wait(i2c); > + if (ret) > + return ret; > + > + cmd = __raw_readq(i2c->twsi_base + SW_TWSI(i2c)); > + if ((cmd & SW_TWSI_R) == 0) > + return octeon_i2c_check_status(i2c, false); > + > + /* read data in FIFO */ > + octeon_i2c_writeq_flush(TWSI_BLOCK_STS_RESET_PTR, i2c->twsi_base + TWSI_BLOCK_STS(i2c)); > + for (i = 0; i < len; i += 8) { > + rd = __raw_readq(i2c->twsi_base + TWSI_BLOCK_FIFO(i2c)); > + for (j = 7; j >= 0; j--) is len always a multiple of 8? > + msgs[1].buf[i + (7 - j)] = (rd >> (8 * j)) & 0xff; > + } > + > + octeon_i2c_block_disable(i2c); > + return ret; > +} [...] > - msgs[1].len > 0 && msgs[1].len <= 8 && > + msgs[1].len > 0 && > msgs[0].addr == msgs[1].addr) { > - if (msgs[1].flags & I2C_M_RD) > - ret = octeon_i2c_hlc_comp_read(i2c, msgs); > - else > - ret = octeon_i2c_hlc_comp_write(i2c, msgs); > - goto out; > + if (msgs[1].len <= 8) { > + if (msgs[1].flags & I2C_M_RD) > + ret = octeon_i2c_hlc_comp_read(i2c, msgs); > + else > + ret = octeon_i2c_hlc_comp_write(i2c, msgs); > + goto out; > + } else if (msgs[1].len <= 1024 && TWSI_BLOCK_CTL(i2c)) { > + if (msgs[1].flags & I2C_M_RD) > + ret = octeon_i2c_hlc_block_comp_read(i2c, msgs); > + else > + ret = octeon_i2c_hlc_block_comp_write(i2c, msgs); > + goto out; > + } the rest looks good... Thanks, Andi
Hi, Andi, On Tue, 2023-09-05 at 12:22 +0200, Andi Shyti wrote: > Hi Aryan, > > In the title, please leave a space after the ':' > > i2c: octeon: Add block-mode r/w > > Please check with "git log drivers..." to see what's the rule in > a particular community. > > I guess Wolfram can fix this, though, before pushing. > > [...] > Done > > +/* high-level-controller composite block write+read, msg0=addr, > > msg1=data */ > > I think this comment is fine and great to have it, but it's > missing a bit of clarity, can you please expand the concept? > Done, let me know if you want me to add more here. > > +static int octeon_i2c_hlc_block_comp_read(struct octeon_i2c *i2c, > > struct i2c_msg *msgs) > > +{ > > + int i, j, len, ret = 0; > > + u64 cmd = 0, rd = 0; > > can please you move rd, j inside the for loop? The basic common > sense is to have all variable declared in the innermost section > in order to avoid confusion. > > It's a nitpick though, not a strong comment and, afaik, not a > real rule. > > Same comment for the function below. > Done, I agree they should be defined within loop. I was just trying to match the other hlc r/w. > > + > > + octeon_i2c_hlc_enable(i2c); > > + octeon_i2c_block_enable(i2c); > > + > > + /* Write (size - 1) into block control register */ > > + len = msgs[1].len - 1; > > + octeon_i2c_writeq_flush((u64)(len), i2c->twsi_base + > > TWSI_BLOCK_CTL(i2c)); > > + > > + /* Prepare core command */ > > + cmd = SW_TWSI_V | SW_TWSI_R | SW_TWSI_SOVR; > > + cmd |= (u64)(msgs[0].addr & 0x7full) << SW_TWSI_ADDR_SHIFT; > > + > > + if (msgs[0].flags & I2C_M_TEN) > > + cmd |= SW_TWSI_OP_10_IA; > > + else > > + cmd |= SW_TWSI_OP_7_IA; > > +No, but this doesnt really matter as the internal j loop will take > > care of the remaining bytes. > > > > e.g. if the len is 9, then we will do > > 0-7 in the first, then i = 8, which is < len, and then the internal > > loop will do 8-17. > > + if (msgs[0].len == 2) { > > + u64 ext = 0; > > + > > + cmd |= SW_TWSI_EIA; > > + ext = (u64)msgs[0].buf[0] << SW_TWSI_IA_SHIFT; > > + cmd |= (u64)msgs[0].buf[1] << SW_TWSI_IA_SHIFT; > > + octeon_i2c_writeq_flush(ext, i2c->twsi_base + > > SW_TWSI_EXT(i2c)); > > + } else { > > + cmd |= (u64)msgs[0].buf[0] << SW_TWSI_IA_SHIFT; > > + } > > This first part is basically a copy/paste with the write() > function... can we put them together in a common function? > > Can we put as much as we can in a single function? > Done. Could not make a common for the write+writes, as they way we insert data into buffers for writing are significantly different, and don't occur after the core command send (i.e. the core command is sent with/concurrently with the write data). Unlike the read, which sends almost identical core commands and reads the buffer differently afterwards. Though if would like it I could mangle together a function for these as well. > > + /* Send command to core (send data to FIFO) */ > > + octeon_i2c_hlc_int_clear(i2c); > > + octeon_i2c_writeq_flush(cmd, i2c->twsi_base + SW_TWSI(i2c)); > > + > > + /* Wait for transaction to complete */ > > + ret = octeon_i2c_hlc_wait(i2c); > > + if (ret) > > + return ret; > > + > > + cmd = __raw_readq(i2c->twsi_base + SW_TWSI(i2c)); > > + if ((cmd & SW_TWSI_R) == 0) > > + return octeon_i2c_check_status(i2c, false); > > + > > + /* read data in FIFO */ > > + octeon_i2c_writeq_flush(TWSI_BLOCK_STS_RESET_PTR, i2c- > > >twsi_base + TWSI_BLOCK_STS(i2c)); > > + for (i = 0; i < len; i += 8) { > > + rd = __raw_readq(i2c->twsi_base + > > TWSI_BLOCK_FIFO(i2c)); > > + for (j = 7; j >= 0; j--) > > is len always a multiple of 8? > > > + msgs[1].buf[i + (7 - j)] = (rd >> (8 * j)) & > > 0xff; > > + } > > + > > + octeon_i2c_block_disable(i2c); > > + return ret; > > +} > > [...] No, but this doesnt really matter as the internal j loop will take care of the remaining bytes. e.g. if the len is 9, then we will do 0-7 in the first, then i = 8, which is < len, and then the internal loop will do 8-17. > > > - msgs[1].len > 0 && msgs[1].len <= 8 && > > + msgs[1].len > 0 && > > msgs[0].addr == msgs[1].addr) { > > - if (msgs[1].flags & I2C_M_RD) > > - ret = octeon_i2c_hlc_comp_read(i2c, > > msgs); > > - else > > - ret = octeon_i2c_hlc_comp_write(i2c, > > msgs); > > - goto out; > > + if (msgs[1].len <= 8) { > > + if (msgs[1].flags & I2C_M_RD) > > + ret = > > octeon_i2c_hlc_comp_read(i2c, msgs); > > + else > > + ret = > > octeon_i2c_hlc_comp_write(i2c, msgs); > > + goto out; > > + } else if (msgs[1].len <= 1024 && > > TWSI_BLOCK_CTL(i2c)) { > > + if (msgs[1].flags & I2C_M_RD) > > + ret = > > octeon_i2c_hlc_block_comp_read(i2c, msgs); > > + else > > + ret = > > octeon_i2c_hlc_block_comp_write(i2c, msgs); > > + goto out; > > + } > > the rest looks good... > > Thanks, > Andi Thanks, Aryan
Hi Andi, Did you have any more comments on my patch? Thank you, Aryan.
diff --git a/drivers/i2c/busses/i2c-octeon-core.c b/drivers/i2c/busses/i2c-octeon-core.c index 845eda70b8ca..940cc4647cb0 100644 --- a/drivers/i2c/busses/i2c-octeon-core.c +++ b/drivers/i2c/busses/i2c-octeon-core.c @@ -130,6 +130,25 @@ static void octeon_i2c_hlc_disable(struct octeon_i2c *i2c) octeon_i2c_ctl_write(i2c, TWSI_CTL_ENAB); } +static void octeon_i2c_block_enable(struct octeon_i2c *i2c) +{ + if (i2c->block_enabled || !TWSI_BLOCK_CTL(i2c)) + return; + + i2c->block_enabled = true; + octeon_i2c_writeq_flush(TWSI_MODE_STRETCH + | TWSI_MODE_BLOCK_MODE, i2c->twsi_base + TWSI_MODE(i2c)); +} + +static void octeon_i2c_block_disable(struct octeon_i2c *i2c) +{ + if (!i2c->block_enabled || !TWSI_BLOCK_CTL(i2c)) + return; + + i2c->block_enabled = false; + octeon_i2c_writeq_flush(TWSI_MODE_STRETCH, i2c->twsi_base + TWSI_MODE(i2c)); +} + /** * octeon_i2c_hlc_wait - wait for an HLC operation to complete * @i2c: The struct octeon_i2c @@ -268,6 +287,7 @@ static int octeon_i2c_start(struct octeon_i2c *i2c) u8 stat; octeon_i2c_hlc_disable(i2c); + octeon_i2c_block_disable(i2c); octeon_i2c_ctl_write(i2c, TWSI_CTL_ENAB | TWSI_CTL_STA); ret = octeon_i2c_wait(i2c); @@ -594,6 +614,124 @@ static int octeon_i2c_hlc_comp_write(struct octeon_i2c *i2c, struct i2c_msg *msg return ret; } +/* high-level-controller composite block write+read, msg0=addr, msg1=data */ +static int octeon_i2c_hlc_block_comp_read(struct octeon_i2c *i2c, struct i2c_msg *msgs) +{ + int i, j, len, ret = 0; + u64 cmd = 0, rd = 0; + + octeon_i2c_hlc_enable(i2c); + octeon_i2c_block_enable(i2c); + + /* Write (size - 1) into block control register */ + len = msgs[1].len - 1; + octeon_i2c_writeq_flush((u64)(len), i2c->twsi_base + TWSI_BLOCK_CTL(i2c)); + + /* Prepare core command */ + cmd = SW_TWSI_V | SW_TWSI_R | SW_TWSI_SOVR; + cmd |= (u64)(msgs[0].addr & 0x7full) << SW_TWSI_ADDR_SHIFT; + + if (msgs[0].flags & I2C_M_TEN) + cmd |= SW_TWSI_OP_10_IA; + else + cmd |= SW_TWSI_OP_7_IA; + + if (msgs[0].len == 2) { + u64 ext = 0; + + cmd |= SW_TWSI_EIA; + ext = (u64)msgs[0].buf[0] << SW_TWSI_IA_SHIFT; + cmd |= (u64)msgs[0].buf[1] << SW_TWSI_IA_SHIFT; + octeon_i2c_writeq_flush(ext, i2c->twsi_base + SW_TWSI_EXT(i2c)); + } else { + cmd |= (u64)msgs[0].buf[0] << SW_TWSI_IA_SHIFT; + } + + /* Send command to core (send data to FIFO) */ + octeon_i2c_hlc_int_clear(i2c); + octeon_i2c_writeq_flush(cmd, i2c->twsi_base + SW_TWSI(i2c)); + + /* Wait for transaction to complete */ + ret = octeon_i2c_hlc_wait(i2c); + if (ret) + return ret; + + cmd = __raw_readq(i2c->twsi_base + SW_TWSI(i2c)); + if ((cmd & SW_TWSI_R) == 0) + return octeon_i2c_check_status(i2c, false); + + /* read data in FIFO */ + octeon_i2c_writeq_flush(TWSI_BLOCK_STS_RESET_PTR, i2c->twsi_base + TWSI_BLOCK_STS(i2c)); + for (i = 0; i < len; i += 8) { + rd = __raw_readq(i2c->twsi_base + TWSI_BLOCK_FIFO(i2c)); + for (j = 7; j >= 0; j--) + msgs[1].buf[i + (7 - j)] = (rd >> (8 * j)) & 0xff; + } + + octeon_i2c_block_disable(i2c); + return ret; +} + +/* high-level-controller composite block write+write, m[0]len<=2, m[1]len<=1024 */ +static int octeon_i2c_hlc_block_comp_write(struct octeon_i2c *i2c, struct i2c_msg *msgs) +{ + bool set_ext = false; + int i, j, len, ret = 0; + u64 cmd, buf = 0, ext = 0; + + octeon_i2c_hlc_enable(i2c); + octeon_i2c_block_enable(i2c); + + /* Write (size - 1) into block control register */ + len = msgs[1].len - 1; + octeon_i2c_writeq_flush((u64)(len), i2c->twsi_base + TWSI_BLOCK_CTL(i2c)); + + /* Prepare core command */ + cmd = SW_TWSI_V | SW_TWSI_SOVR; + cmd |= (u64)(msgs[0].addr & 0x7full) << SW_TWSI_ADDR_SHIFT; + + if (msgs[0].flags & I2C_M_TEN) + cmd |= SW_TWSI_OP_10_IA; + else + cmd |= SW_TWSI_OP_7_IA; + + if (msgs[0].len == 2) { + cmd |= SW_TWSI_EIA; + ext |= (u64)msgs[0].buf[0] << SW_TWSI_IA_SHIFT; + set_ext = true; + cmd |= (u64)msgs[0].buf[1] << SW_TWSI_IA_SHIFT; + } else { + cmd |= (u64)msgs[0].buf[0] << SW_TWSI_IA_SHIFT; + } + + /* Write msg into FIFO buffer */ + octeon_i2c_writeq_flush(TWSI_BLOCK_STS_RESET_PTR, i2c->twsi_base + TWSI_BLOCK_STS(i2c)); + for (i = 0; i < len; i += 8) { + buf = 0; + for (j = 7; j >= 0; j--) + buf |= (msgs[1].buf[i + (7 - j)] << (8 * j)); + octeon_i2c_writeq_flush(buf, i2c->twsi_base + TWSI_BLOCK_FIFO(i2c)); + } + if (set_ext) + octeon_i2c_writeq_flush(ext, i2c->twsi_base + SW_TWSI_EXT(i2c)); + + /* Send command to core (send data in FIFO) */ + octeon_i2c_hlc_int_clear(i2c); + octeon_i2c_writeq_flush(cmd, i2c->twsi_base + SW_TWSI(i2c)); + + /* Wait for transaction to complete */ + ret = octeon_i2c_hlc_wait(i2c); + if (ret) + goto ret; + + cmd = __raw_readq(i2c->twsi_base + SW_TWSI(i2c)); + if ((cmd & SW_TWSI_R) == 0) + return octeon_i2c_check_status(i2c, false); + + octeon_i2c_block_disable(i2c); + return ret; +} + /** * octeon_i2c_xfer - The driver's master_xfer function * @adap: Pointer to the i2c_adapter structure @@ -619,13 +757,21 @@ int octeon_i2c_xfer(struct i2c_adapter *adap, struct i2c_msg *msgs, int num) if ((msgs[0].flags & I2C_M_RD) == 0 && (msgs[1].flags & I2C_M_RECV_LEN) == 0 && msgs[0].len > 0 && msgs[0].len <= 2 && - msgs[1].len > 0 && msgs[1].len <= 8 && + msgs[1].len > 0 && msgs[0].addr == msgs[1].addr) { - if (msgs[1].flags & I2C_M_RD) - ret = octeon_i2c_hlc_comp_read(i2c, msgs); - else - ret = octeon_i2c_hlc_comp_write(i2c, msgs); - goto out; + if (msgs[1].len <= 8) { + if (msgs[1].flags & I2C_M_RD) + ret = octeon_i2c_hlc_comp_read(i2c, msgs); + else + ret = octeon_i2c_hlc_comp_write(i2c, msgs); + goto out; + } else if (msgs[1].len <= 1024 && TWSI_BLOCK_CTL(i2c)) { + if (msgs[1].flags & I2C_M_RD) + ret = octeon_i2c_hlc_block_comp_read(i2c, msgs); + else + ret = octeon_i2c_hlc_block_comp_write(i2c, msgs); + goto out; + } } } diff --git a/drivers/i2c/busses/i2c-octeon-core.h b/drivers/i2c/busses/i2c-octeon-core.h index 9bb9f64fdda0..81fcf413c890 100644 --- a/drivers/i2c/busses/i2c-octeon-core.h +++ b/drivers/i2c/busses/i2c-octeon-core.h @@ -85,6 +85,11 @@ #define TWSI_INT_SDA BIT_ULL(10) #define TWSI_INT_SCL BIT_ULL(11) +#define TWSI_MODE_STRETCH BIT_ULL(1) +#define TWSI_MODE_BLOCK_MODE BIT_ULL(2) + +#define TWSI_BLOCK_STS_RESET_PTR BIT_ULL(0) +#define TWSI_BLOCK_STS_BUSY BIT_ULL(1) #define I2C_OCTEON_EVENT_WAIT 80 /* microseconds */ /* Register offsets */ @@ -92,11 +97,19 @@ struct octeon_i2c_reg_offset { unsigned int sw_twsi; unsigned int twsi_int; unsigned int sw_twsi_ext; + unsigned int twsi_mode; + unsigned int twsi_block_ctl; + unsigned int twsi_block_sts; + unsigned int twsi_block_fifo; }; #define SW_TWSI(x) (x->roff.sw_twsi) #define TWSI_INT(x) (x->roff.twsi_int) #define SW_TWSI_EXT(x) (x->roff.sw_twsi_ext) +#define TWSI_MODE(x) (x->roff.twsi_mode) +#define TWSI_BLOCK_CTL(x) (x->roff.twsi_block_ctl) +#define TWSI_BLOCK_STS(x) (x->roff.twsi_block_sts) +#define TWSI_BLOCK_FIFO(x) (x->roff.twsi_block_fifo) struct octeon_i2c { wait_queue_head_t queue; @@ -110,6 +123,7 @@ struct octeon_i2c { void __iomem *twsi_base; struct device *dev; bool hlc_enabled; + bool block_enabled; bool broken_irq_mode; bool broken_irq_check; void (*int_enable)(struct octeon_i2c *); diff --git a/drivers/i2c/busses/i2c-thunderx-pcidrv.c b/drivers/i2c/busses/i2c-thunderx-pcidrv.c index a77cd86fe75e..abde98117d7e 100644 --- a/drivers/i2c/busses/i2c-thunderx-pcidrv.c +++ b/drivers/i2c/busses/i2c-thunderx-pcidrv.c @@ -165,6 +165,10 @@ static int thunder_i2c_probe_pci(struct pci_dev *pdev, i2c->roff.sw_twsi = 0x1000; i2c->roff.twsi_int = 0x1010; i2c->roff.sw_twsi_ext = 0x1018; + i2c->roff.twsi_mode = 0x1038; + i2c->roff.twsi_block_ctl = 0x1048; + i2c->roff.twsi_block_sts = 0x1050; + i2c->roff.twsi_block_fifo = 0x1058; i2c->dev = dev; pci_set_drvdata(pdev, i2c);
Add support for block mode read/write operations on Thunderx chips. When attempting r/w operations of greater then 8 bytes block mode is used, instead of performing a series of 8 byte reads. Signed-off-by: Aryan Srivastava <aryan.srivastava@alliedtelesis.co.nz> --- Changes in v2: - comment style and formatting. Changes in v3: - comment style and formatting. --- drivers/i2c/busses/i2c-octeon-core.c | 158 ++++++++++++++++++++++- drivers/i2c/busses/i2c-octeon-core.h | 14 ++ drivers/i2c/busses/i2c-thunderx-pcidrv.c | 4 + 3 files changed, 170 insertions(+), 6 deletions(-)