On Fri, 24 Feb 2017, Peter Maydell wrote:
On 19 February 2017 at 16:35, BALATON Zoltan <bala...@eik.bme.hu> wrote:
Write only to allow clients to initialise these without failing
Signed-off-by: BALATON Zoltan <bala...@eik.bme.hu>
What's the point in write-only register values?
U-boot writes this register during setting up the device and without this
it would abort QEMU.
What does the real hardware do here?
This register contains bits to set up FIFO parameters and memory
priorities which we are not emulating so these can be ignored here but
the hardware would change parameters according the value written.
If the registers are writes-ignored, there's no need to store
the data written into the state struct; if the registers are
reads-as-written then implement them that way.
I'm not sure what you get on real hardware but it's documented to be R/W
(except reserved bits that are masked which are always 0). Why is it not
implemented as read-as-written or what do you mean by that?
