RFC i2c: core: introduce master_xfer_irqless
Get series with b4
b4 am 20180920225608.GD988@kunaiVersions newest first
- v1 RFC Latest4 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | i2c: core: remove outdated DEBUG output | +0 | 0 replies | |
| 2/4 | i2c: core: remove level of indentation in i2c_transfer | +0 | 0 replies | |
| 2/4 | i2c: core: remove level of indentation in i2c_transfer | +0 | 0 replies | |
| 3/4 | i2c: core: use I2C locking behaviour also for SMBUS | +0 | 0 replies | |
| 4/4 | i2c: core: introduce master_xfer_irqless callback | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/4] i2c: core: introduce master_xfer_irqless
Quoted 10 lines · Wolfram Sang
To keep the discussion about
master_xfer_irqlessgoing, I post here a draft how I envision the changes to the I2C core. They are only build tested. I am unsure if I can test them on hardware before next week, so I'll send them around as RFC already, so people can get an idea and comment. Maybe Stefan has some bandwidth to test his imx driver implementation on top of this?A branch can be found here:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.gitrenesas/i2c/xfer_irqless
What I forgot to mention:
At some point, I'd like an adiitional check if the device is flagged to have very late I2C transfers and trigger a fat warning if not. To keep bugs visible.
I have ideas but not perfect yet, so I'll leave this as the next step.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180921/79fdf3e8/attachment.sig>