From: Sultan Alsawaf <sultan@kerneltoast.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: aaron.ma@canonical.com, admin@kryma.net,
andriy.shevchenko@linux.intel.com, benjamin.tissoires@redhat.com,
hdegoede@redhat.com, hn.chen@weidahitech.com, jikos@kernel.org,
kai.heng.feng@canonical.com, linux-i2c@vger.kernel.org,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
mika.westerberg@linux.intel.com, vicamo.yang@canonical.com,
wsa@kernel.org
Subject: Re: [PATCH v2] HID: i2c-hid: Use block reads when possible to save power
Date: Wed, 1 Jul 2020 08:00:07 -0700 [thread overview]
Message-ID: <20200701150007.GA2141@sultan-book.localdomain> (raw)
In-Reply-To: <ef949533-c614-7afb-f206-5c54d827deac@linux.intel.com>
On Wed, Jul 01, 2020 at 11:04:01AM +0300, Jarkko Nikula wrote:
> On 6/29/20 8:43 PM, Sultan Alsawaf wrote:
> > Hmm, for some reason in 5.8 I get the same problem, but 5.7 is fine. Could you
> > try this on 5.7 and see if it works?
> >
> > In the meantime I'll bisect 5.8 to see why it's causing problems for me...
> >
> I see the same issue on top of v5.7:
Try reverting my "i2c: designware: Only check the first byte for SMBus block
read length" patch and apply the following change instead:
--- a/drivers/i2c/busses/i2c-designware-master.c
+++ b/drivers/i2c/busses/i2c-designware-master.c
@@ -394,10 +394,12 @@ i2c_dw_read(struct dw_i2c_dev *dev)
u32 flags = msgs[dev->msg_read_idx].flags;
*buf = dw_readl(dev, DW_IC_DATA_CMD);
- /* Ensure length byte is a valid value */
- if (flags & I2C_M_RECV_LEN &&
- *buf <= I2C_SMBUS_BLOCK_MAX && *buf > 0) {
- len = i2c_dw_recv_len(dev, *buf);
+ if (flags & I2C_M_RECV_LEN) {
+ /* Ensure length byte is a valid value */
+ if (*buf <= I2C_SMBUS_BLOCK_MAX && *buf > 0)
+ len = i2c_dw_recv_len(dev, *buf);
+ else
+ len = i2c_dw_recv_len(dev, len);
}
buf++;
dev->rx_outstanding--;
next prev parent reply other threads:[~2020-07-01 15:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 21:02 [PATCH 0/2] i2c-hid: Save power by reducing i2c xfers with block reads Sultan Alsawaf
2020-06-14 21:02 ` [PATCH 1/2] i2c: designware: Only check the first byte for SMBus block read length Sultan Alsawaf
2020-06-15 9:40 ` Andy Shevchenko
2020-06-15 16:03 ` Sultan Alsawaf
2020-06-15 16:07 ` Andy Shevchenko
2020-06-15 17:15 ` Sultan Alsawaf
2020-06-16 13:22 ` Jarkko Nikula
2020-06-16 15:43 ` [PATCH v2] " Sultan Alsawaf
2020-06-17 11:08 ` Jarkko Nikula
2020-06-14 21:02 ` [PATCH 2/2] HID: i2c-hid: Use block reads when possible to save power Sultan Alsawaf
2020-06-16 13:43 ` Jarkko Nikula
2020-06-16 15:49 ` [PATCH v2] " Sultan Alsawaf
2020-06-16 16:41 ` Andy Shevchenko
2020-06-16 17:18 ` Andi Shyti
2020-06-16 17:32 ` Sultan Alsawaf
2020-06-16 18:02 ` Andi Shyti
2020-06-16 18:17 ` Sultan Alsawaf
2020-06-17 11:17 ` Jarkko Nikula
2020-06-29 17:43 ` Sultan Alsawaf
2020-07-01 8:04 ` Jarkko Nikula
2020-07-01 15:00 ` Sultan Alsawaf [this message]
2020-07-03 11:18 ` Jarkko Nikula
2020-09-14 0:15 ` [PATCH v3] i2c: Squash of SMBus block read patchset " Sultan Alsawaf
[not found] ` <bcf9cd02-13d1-8f87-8ef9-2f05f0b54808@linux.intel.com>
2020-09-15 17:48 ` Sultan Alsawaf
2020-09-16 14:09 ` Jarkko Nikula
2020-09-15 20:44 ` Jiri Kosina
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=20200701150007.GA2141@sultan-book.localdomain \
--to=sultan@kerneltoast.com \
--cc=aaron.ma@canonical.com \
--cc=admin@kryma.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=hdegoede@redhat.com \
--cc=hn.chen@weidahitech.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jikos@kernel.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=vicamo.yang@canonical.com \
--cc=wsa@kernel.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).