The author says setting a register like this is hard to read and maintain:

    *(volatile std::uint32_t*)reg_name = val;

And the author's solution is to replace that one line with this:

    struct DeviceSetup {
        enum class TableType : std::uint32_t {
            inphase = 0,
            quadrature,
            table
        };

        std::uint32_t input_source : 8;
        TableType table_type : 4;
        std::uint32_t reserved : 20;
    };

    volatile auto device_registers_ptr = reinterpret_cast<DeviceSetup*>(DeviceControlAddress);

I'm not really seeing the readability and maintainability advantages here.