SoylentNews is people
SoylentNews
https://www.devever.net/~hl/regmap
If you've ever had to write a program which interfaces directly with hardware â perhaps while writing a program for an MCU or embedded system or a kernel driver â you may have noticed a few common patterns in register map behaviour and design. I'm not sure anyone has ever really collected them together, so I decided to make a list of all the ones I can think of.
This discussion was created by janrinok (52) for logged-in users only. Log in and try again!
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
I think that I shall never see
A billboard lovely as a tree.
Indeed, unless the billboards fall
I'll never see a tree at all.
-- Ogden Nash
(Score: 2) by Mojibake Tengu on Monday May 22, @11:05PM
Write-only registers are usually used for controlling such hardware state, where reading back does not have any sense because the state itself is rather ephemeral in time domain (because it serializes, or just strobes some other data).
Some examples are tape or floppy interfaces, or full duplex modem control.
Today, it's still usual as GPIO set in OUT mode.
Another fine example is power-off control. You don't want to read power control to determine the machine is powered off, don't you?
The edge of ċ¤Şç cannot be defined, for it is beyond every aspect of design