Acpi 80860f14 Best

---

Title: Handling ACPI 80860F14 (Intel Bay Trail I2C Controller) on Linux

Post:

I'm encountering the ACPI device ID 80860F14 on an Intel Atom Bay Trail (e.g., Z3735F, Z3736G) based system.

Context:

• ACPI ID: 80860F14
• Hardware: Intel Bay Trail-T I2C Controller #5 (or general purpose controller).
• Driver: Typically handled by pinctrl-baytrail or designware_i2c (dw_i2c).
• Issue: On some kernels (especially < 5.4 or custom builds), this device fails to probe correctly, leading to missing touchscreen, sensor, or GPIO expander functionality.

Symptoms:

• dmesg shows: i2c_designware 80860F14:00: Unknown Synopsys I2C bus type
• Or the device remains hidden/unbound despite CONFIG_I2C_DESIGNWARE_PLATFORM=y.

Root Cause: The ACPI driver binding for this ID requires specific handling because the Bay Trail I2C controllers are not fully compliant with the standard Synopsys DesignWare I2C IP block. They need a "semaphore" mechanism to coordinate with the P-unit (Power Management unit).

Fix / Workaround:

1. Kernel Configuration: Ensure these options are enabled (not just modular):

   CONFIG_I2C_DESIGNWARE_CORE=y
   CONFIG_I2C_DESIGNWARE_PLATFORM=y
   CONFIG_I2C_DESIGNWARE_BAYTRAIL=y   # Critical for this ID
   

2. Kernel Command Line (if still failing): Add intel_idle.max_cstate=1 to grub. This prevents the P-unit from entering deep C-states that break the I2C semaphore. Acpi 80860f14

3. Check ACPI Status:

   ls /sys/bus/acpi/devices/80860F14:00/
   cat /sys/bus/acpi/devices/80860F14:00/status
   

   Expected status: 15 (present, enabled, shown, functioning).

Final note: On mainline kernels 5.10+, this ID should be automatically handled by dw_i2c via the baytrail_sem_platform quirk. If you still see errors, check your DSDT for custom modifications or consider updating your firmware.

Does anyone have a device tree or ACPI overlay for this ID to manually assign the pinctrl-single properties?

---

The hardware ID ACPI\80860F14 refers to the Intel Serial IO I2C Controller.

Here is a detailed breakdown of what this device is, why it appears in your Device Manager (usually as an "Unknown Device"), and how to fix it.

What is it?

This device is responsible for managing power states for the processor and other system components. If the driver is missing, your computer may not sleep or wake up correctly, or you may see a generic "Unknown Device" in your device list.

Solutions and Workarounds for ACPI 80860F14

Depending on your operating system and use case, here are the proven methods to address the ACPI 80860F14 issue. Title: Handling ACPI 80860F14 (Intel Bay Trail I2C

2. Hardware Context

• Vendor: Intel Corporation (8086)
• Device ID: 0F14 (hex)
• Common SoCs: Bay Trail-T (e.g., Atom Z37xx series), Cherry Trail (Atom x5/x7)
• Typical Function: I2C controller #4 or a general-purpose power management sequencer.

On Bay Trail, this device often acts as a GPIO/I2C bridge for touchscreens, sensors, and other peripheral control.

Solution 1: Intel Chipset Driver Installation (Recommended)

Intel no longer provides explicit "Bay Trail I2C" drivers on their main website. Instead, they are bundled within the Intel SOC (System-on-Chip) Driver Set.

1. Visit your device manufacturer’s support website (Dell, HP, Lenovo, Acer, Asus).
2. Enter your product’s service tag or model number.
3. Download and install the Intel Chipset Driver and the Intel Serial IO Driver.
   • The Serial IO driver package includes drivers for I2C, GPIO, SPI, and UART.
4. Reboot your system.

For custom builds or generic tablets:

• Search for Intel Serial IO Driver for Windows 10/11.
• Ensure you download version 30.100.1725.1 or later for Cherry Trail.

3. How to fix the driver issue

If your touchpad, touchscreen, or other sensors are not working, you need to install the correct driver.

For Linux Users: The 5-Step Fix

Most modern distributions (Ubuntu 20.04+, Fedora 34+, Arch Linux) include the necessary drivers, but they may need to be manually triggered.

Step 1: Identify Your Audio Codec Open a terminal and run:

sudo dmesg | grep -i "sst"
sudo i2cdetect -l (if i2c-tools installed)

Look for references to "byt" or "cht" and a codec ID like RT5640, RT5651, or ES8316.

Step 2: Load the Correct Machine Driver The machine driver tells the SST core how to talk to 80860F14. For most Bay Trail devices: ACPI ID: 80860F14 Hardware: Intel Bay Trail-T I2C

sudo modprobe snd_soc_sst_bytcr_rt5640

If that fails, try:

sudo modprobe snd_soc_sst_bytcr_rt5651
sudo modprobe snd_soc_sst_cht_bsw_rt5672

Step 3: Force ACPI ID Matching (Kernel Parameter) Add the following to your bootloader (GRUB) kernel command line:

snd_intel_sst.acpi_path=80860F14

Or for newer kernels using SOF (Sound Open Firmware):

sof_pci_debug=1

Step 4: Install Firmware (Critical for DSP) The SST DSP requires non-free firmware. Install the linux-firmware package, ensuring /lib/firmware/intel/ contains:

• sst.bin
• intel/sof/sof-byt.ri
• intel/sof-tplg/sof-byt-rt5640.tplg

On Debian/Ubuntu: sudo apt install firmware-intel-sound

Step 5: Blacklist Conflicting Drivers Sometimes the legacy snd_hda_intel grabs the PCI slot. Blacklist it in /etc/modprobe.d/blacklist.conf:

blacklist snd_hda_intel

After a reboot, aplay -l should show your analog audio device.

Method B: Manual Download from Manufacturer Website

If you prefer to download the file manually, you must get it from your laptop manufacturer's support page (e.g., Dell, HP, Lenovo, ASUS) or Intel directly.

1. Go to your laptop manufacturer's support website.
2. Search for your specific laptop model.
3. Look for the Drivers & Downloads section.
4. Look for a driver named "Intel Serial IO Driver".
   • Note: It may also be bundled inside a "Chipset Driver" package.
5. Download and install the driver, then restart your computer.