waskie Posted July 12, 2012 Report Share Posted July 12, 2012 I think the volatile flag should adjust the behaviour of writeable fields. Currently, if the mirrored value and desired value are the same, it is determined a field is unchanged and a write may not happen (needs_update() returns a zero). However, if the field is flagged as volatile (i.e. the hardware can change the value behind-the-scenes) we can't count on the mirrored value as being accurate. I think needs_update() should return a 1 in this case - if the user is requesting an update it's because he/she wants to ensure the hardware is as a known value. It seems wasteful to have to perform a bus read first to see if the field needs updating (and it's a bit of a hack to call predict() to change the mirrored value). Shane Quote Link to comment Share on other sites More sharing options...
janick Posted July 12, 2012 Report Share Posted July 12, 2012 Seems reasonable. Just filed an enhancement request: http://www.eda.org/svdb/view.php?id=4253 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.