SSDT-HPET - how to tell do you really need it?

[atanvarno]

Ever since I started this little hobby, first step was to fire-up SSDTTime, generate HPET one and dutifully add it to my EFI. But I wonder — how can I really tell I need it?
I tested my build without it (and related patches) and audio through back I/O headphone jack works.

DSDT has this for HPET:

    Device (HPET)
    {
...
        Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
        {
            Name (BUF0, ResourceTemplate ()
            {
                IRQNoFlags ()
                    {0}
                IRQNoFlags ()
                    {8}
                Memory32Fixed (ReadOnly,
                    0xFED00000,         // Address Base
                    0x00000400,         // Address Length
                    )
            })
            Return (BUF0) /* \HPET._CRS.BUF0 */
        }
    }

and this is what SSDT-Time generated:

DefinitionBlock ("", "SSDT", 2, "CORP", "HPET", 0x00000000)
{
    External (HPET, DeviceObj)

    Name (\HPET._CRS, ResourceTemplate ()  // _CRS: Current Resource Settings
    {
        IRQNoFlags ()
            {0,8,11}
        Memory32Fixed (ReadWrite,
            0xFED00000,         // Address Base
            0x00000400,         // Address Length
            )
    })
}

Apart from Interupt 11, looks pretty much the same.

What would be the tell-tale sign in DSDT that one needs custom SSDT-HPET?

 

[ExtremeXT]

Ever since I started this little hobby, first step was to fire-up SSDTTime, generate HPET one and dutifully add it to my EFI. But I wonder — how can I really tell I need it?
I tested my build without it (and related patches) and audio through back I/O headphone jack works.

DSDT has this for HPET:

    Device (HPET)
    {
...
        Method (_CRS, 0, NotSerialized)  // _CRS: Current Resource Settings
        {
            Name (BUF0, ResourceTemplate ()
            {
                IRQNoFlags ()
                    {0}
                IRQNoFlags ()
                    {8}
                Memory32Fixed (ReadOnly,
                    0xFED00000,         // Address Base
                    0x00000400,         // Address Length
                    )
            })
            Return (BUF0) /* \HPET._CRS.BUF0 */
        }
    }

and this is what SSDT-Time generated:

DefinitionBlock ("", "SSDT", 2, "CORP", "HPET", 0x00000000)
{
    External (HPET, DeviceObj)

    Name (\HPET._CRS, ResourceTemplate ()  // _CRS: Current Resource Settings
    {
        IRQNoFlags ()
            {0,8,11}
        Memory32Fixed (ReadWrite,
            0xFED00000,         // Address Base
            0x00000400,         // Address Length
            )
    })
}

Apart from Interupt 11, looks pretty much the same.

What would be the tell-tale sign in DSDT that one needs custom SSDT-HPET?

AMD CPUs shouldn't need HPET at all, usually only older Intel CPUs or obscure Intel prebuilt PCs do.