On Tue, Jan 11, 2022 at 10:13:43AM +0000, Lee Jones wrote: > Unless something has changed or my understanding is not correct, > regmap does not support over-lapping register ranges. If there's no caches and we're always going direct to hardware it will work a lot of the time since the buses generally have concurrency protection at the lowest level, though if the drivers ever do any read/modify/write operations the underlying hardware bus isn't going to know about it so you could get data corruption if two drivers decide to try to operate on the same register. If there's caches things will probably go badly since the cache will tend to amplify the read/modify/write issues. > However, even if that is required, I still think we can come up with > something cleaner than creating a whole API based around creating > and fetching different regmap configurations depending on how the > system was initialised. Yeah, I'd expect the usual pattern is to have wrapper drivers that instantiate a regmap then have the bulk of the driver be a library that they call into should work.
Attachment:
signature.asc
Description: PGP signature
