On Mon, Sep 20, 2021 at 09:37:37PM +0200, Peter Rosin wrote: > compare if the update was needed at all. But marking volatile wasn't > enough. I also tried to set both a default and mark as volatile, > but it seems every read fails with -16 (EBUSY). I don't get why, to me > it almost feels like a regmap issue of some sort (probably the regmap > config is bad in some way), but I'm not fluent in regmap... Having a default for a volatile register isn't really a sensible configuration since the whole point with volatile registers is that they change underneath us, I'd not be surprised if we had some error checking code in there that was trying to tell you there was a problem though it does seem like it should at least be more verbose about it since returning -EBUSY isn't exactly helpful by itself.
Attachment:
signature.asc
Description: PGP signature
