Re: [RFC PATCH 1/4] i2c: allow drivers to announce that they are IRQ safe

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2018-09-03 19:21, Wolfram Sang wrote:
> 
>> Then I vote for extending the 'struct i2c_algorithm' with an extra
>> callback 'master_xfer_irqless'. The idea was already proposed here.
> 
> Yes, I proposed the idea a few times and now I cooked up an RFC.
> Only build tested and merely a starter for discussion.
> 
> Let me know what you think, people.

There is still the "if (in_atomic() || irqs_disabled())" thing in
i2c_transfer(), something we did not replicate in the recent
rework of i2c_smbus_xfer()

Do we not need to do that dance in i2c_smbus_xfer() too and as apart
of that add ->smbus_xfer_irqless?

My guess was that many things that needs to be done "late" are
performed as one of the i2c_smbus_read/write... calls, but what do I
know? Or maybe I'm just too far ahead?

Cheers,
Peter



[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux