Hi,
On 25-09-18 18:29, Wolfram Sang wrote:
Anyways with that said I'm fine with changing this to -EBUSY, that
was my initial thought on this to.
Please let me know how you want to proceed with this
(which error code you want to use).
FYI: I am just now in the process of designing this behaviour into the
core (like with a flag to enable it). It is open coded by various
drivers, and often with issues.
Sounds good, let me know when you've something ready for
review/testing. I can reproduce the problem of accessing the
i2c bus while suspended at will by reverting one of the
ordering fixes I recently did, so I can happily test such
a generic fix.
Also I assume you want to not merge this patch then in favor
of going with the generic solution you are working on?
Regards,
Hans
