On Thu, Nov 01, 2018 at 10:28:28AM +0000, Charles Keepax wrote: > 1.2) Read all the registers from the device on boot > + Uses less memory > - Potentially very slow boot time > 1.3) Only read values as you touch registers > + Uses less memory > + Usually no significant impact on boot time > - Can't do read or read/write/modify operations on > previously untouched registers whilst chip is off Both of these options also require that you be able to reset the device which isn't possible with all devices and systems. > I think this really the crux of my concerns here about updating > the regmap API are that it feels like almost any path we take > from here results in worse runtime performance and probably > equal or worse memory usage. In return we gain a reduction of > some, whilst admittedly large, very simple data tables from > the driver. Which is a trade it feels hard to get invested in. Right, I don't see an urgent problem either - if the tables were complicated to think about it'd be a bit different but they aren't particularly and like you say there's tradeoffs both at runtime and at development time for trying to make the source code smaller. Equally if there are useful things we can add to the API for some use cases I'm all for that so long as they don't get in the way of other users, most of the extensions in the API have come from someone having problems and coming up with a fix that meets their needs.
Attachment:
signature.asc
Description: PGP signature
