Lines Matching +full:64 +full:bit

330      * Bit width field in the GAS is only one byte long, 255 max.  in AcpiTbInitGenericAddress()
344 "%s - 32-bit FADT register is too long (%u bytes, %u bits) " in AcpiTbInitGenericAddress()
353 * The 64-bit Address field is non-aligned in the byte packed in AcpiTbInitGenericAddress()
372 * Address32 - 32-bit address of the register
373 * Address64 - 64-bit address of the register
375 * RETURN: The resolved 64-bit address
377 * DESCRIPTION: Select between 32-bit and 64-bit versions of addresses within
383 * the 32-bit and 64-bit address fields (FIRMWARE_CTRL/X_FIRMWARE_CTRL and
388 * By default, as per the ACPICA specification, a valid 64-bit address is
389 * used regardless of the value of the 32-bit address. However, this
403 /* 64-bit address is zero, use 32-bit address */ in AcpiTbSelectAddress()
411 /* Address mismatch between 32-bit and 64-bit versions */ in AcpiTbSelectAddress()
414 "32/64X %s address mismatch in FADT: " in AcpiTbSelectAddress()
415 "0x%8.8X/0x%8.8X%8.8X, using %u-bit address", in AcpiTbSelectAddress()
417 AcpiGbl_Use32BitFadtAddresses ? 32 : 64)); in AcpiTbSelectAddress()
419 /* 32-bit address override */ in AcpiTbSelectAddress()
427 /* Default is to use the 64-bit address */ in AcpiTbSelectAddress()
581 * Expand 32-bit addresses to 64-bit as necessary. Also validate
587 * Notes on 64-bit register addresses:
589 * After this FADT conversion, later ACPICA code will only use the 64-bit "X"
592 * The 64-bit X fields are optional extensions to the original 32-bit FADT
595 * 32-bit V1.0 fields to the 64-bit X fields if the 64-bit X field is originally
598 * For ACPI 1.0 FADTs (that contain no 64-bit addresses), all 32-bit address
599 * fields are expanded to the corresponding 64-bit X fields in the internal
602 * For ACPI 2.0+ FADTs, all valid (non-zero) 32-bit address fields are expanded
603 * to the corresponding 64-bit X fields, if the 64-bit field is originally
604 * zero. Adhering to the ACPI specification, we completely ignore the 32-bit
605 * field if the 64-bit field is valid, regardless of whether the host OS is
606 * 32-bit or 64-bit.
655 * Expand the 32-bit DSDT addresses to 64-bit as necessary. in AcpiTbConvertFadt()
656 * Later ACPICA code will always use the X 64-bit field. in AcpiTbConvertFadt()
668 /* Examine all of the 64-bit extended address fields (X fields) */ in AcpiTbConvertFadt()
673 * Get the 32-bit and 64-bit addresses, as well as the register in AcpiTbConvertFadt()
689 * Expand the ACPI 1.0 32-bit addresses to the ACPI 2.0 64-bit "X" in AcpiTbConvertFadt()
691 * the 64-bit address structures. in AcpiTbConvertFadt()
694 * Now always use the 64-bit address if it is valid (non-zero), in in AcpiTbConvertFadt()
695 * accordance with the ACPI specification which states that a 64-bit in AcpiTbConvertFadt()
696 * address supersedes the 32-bit version. This behavior can be in AcpiTbConvertFadt()
699 * During 64-bit address construction and verification, in AcpiTbConvertFadt()
714 * Note: SpaceId is always I/O for 32-bit legacy address fields in AcpiTbConvertFadt()
725 "32/64X address mismatch in FADT/%s: " in AcpiTbConvertFadt()
726 "0x%8.8X/0x%8.8X%8.8X, using %u-bit address", in AcpiTbConvertFadt()
729 AcpiGbl_Use32BitFadtAddresses ? 32 : 64)); in AcpiTbConvertFadt()
735 * 64-bit X length field. in AcpiTbConvertFadt()
738 * 64-bit GAS structure can accommodate, 0xFF bits). in AcpiTbConvertFadt()
744 "32/64X length mismatch in FADT/%s: %u/%u", in AcpiTbConvertFadt()
750 * Hardware register access code always uses the 64-bit fields. in AcpiTbConvertFadt()
751 * So if the 64-bit field is zero or is to be overridden, in AcpiTbConvertFadt()
752 * initialize it with the 32-bit fields. in AcpiTbConvertFadt()
753 * Note that when the 32-bit address favor is specified, the in AcpiTbConvertFadt()
754 * 64-bit fields are always re-initialized so that in AcpiTbConvertFadt()
756 * configured to the values to trigger a 32-bit compatible in AcpiTbConvertFadt()