Bug 8972

Summary: failed to add I2C device MSFT8000:00 from ACPI on MinnowBoard Max
Product: [Hardware Platforms] MinnowBoard MAX Firmware Reporter: California Sullivan <california.l.sullivan>
Component: minnowboard-firmwareAssignee: He, Tim <tim.he>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Undecided CC: david.wei, mike.wu
Version: unspecified   
Target Milestone: ---   
Hardware: MinnowBoard Max   
OS: x86_64   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description California Sullivan 2016-01-21 19:10:24 UTC
The following error message occurs on a 4.4 Linux kernel:

[   28.836018] i2c i2c-7: Invalid 7-bit I2C address 0xff
[   28.908036] i2c i2c-7: failed to add I2C device MSFT8000:00 from ACPI

The reason this happens is because the 4.4 kernel adds an i2c_check_addr_validty call to the acpi_i2c_add_device function. This call returns a failure because that device is defined as having a 7 bit address and an address 0x00ff (which is 8 bits) in the ACPI tables:

            Name (_HID, "MSFT8000")  // _HID: Hardware ID
            Name (_CID, "MSFT8000")  // _CID: Compatible ID
            Name (_UID, One)  // _UID: Unique ID
            Name (_CRS, ResourceTemplate ()  // _CRS: Current Resource Settings
            {
            ...
               I2cSerialBus (0x00FF, ControllerInitiated, 0x00061A80,
                    AddressingMode7Bit, "\\_SB.I2C6",
                    0x00, ResourceConsumer, ,
                    )
            ...
Comment 1 He, Tim 2016-03-02 06:50:59 UTC
Cal, I'd like to verify this bug, could you please tell me where to download the new Yocto image with 4.4 Linux kernel? thanks.
Comment 2 David_Wei 2016-03-11 02:58:55 UTC
Tim,

If you still do not know how to verify it, could you attach a test image for California to help test? Let's work together to make this fix available on V0.91 firmware release.
Comment 3 He, Tim 2016-03-24 07:39:00 UTC
Fix this issue on next release (0.91).
Comment 4 California Sullivan 2016-08-10 23:01:02 UTC
Confirmed fixed. If anyone still sees this bug, please update your firmware to the latest version.