x86: fsp: Call fsp_init_phase_pci() in pci_uclass_post_probe()

[u-boot] / drivers / i2c / Kconfig

diff --git a/drivers/i2c/Kconfig b/drivers/i2c/Kconfig
index e861b536863a30d272b1fc8c68e287df8d56e285..c40bd5c1e069749b5d06aac02b89e12f2d2789b6 100644 (file)
--- a/drivers/i2c/Kconfig
+++ b/drivers/i2c/Kconfig
@@ -1,3 +1,9 @@
+#
+# I2C subsystem configuration
+#
+
+menu "I2C support"
+
 config DM_I2C
        bool "Enable Driver Model for I2C drivers"
        depends on DM
@@ -29,6 +35,19 @@ config I2C_CROS_EC_TUNNEL
          I2C or LPC). Some Chromebooks use this when the hardware design
          does not allow direct access to the main PMIC from the AP.
 
+config I2C_CROS_EC_LDO
+       bool "Provide access to LDOs on the Chrome OS EC"
+       depends on CROS_EC
+       ---help---
+       On many Chromebooks the main PMIC is inaccessible to the AP. This is
+       often dealt with by using an I2C pass-through interface provided by
+       the EC. On some unfortunate models (e.g. Spring) the pass-through
+       is not available, and an LDO message is available instead. This
+       option enables a driver which provides very basic access to those
+       regulators, via the EC. We implement this as an I2C bus which
+       emulates just the TPS65090 messages we know about. This is done to
+       avoid duplicating the logic in the TPS65090 regulator driver for
+       enabling/disabling an LDO.
 
 config DM_I2C_GPIO
        bool "Enable Driver Model for software emulated I2C bus driver"
@@ -86,3 +105,5 @@ config SYS_I2C_UNIPHIER_F
          This I2C controller is used on PH1-Pro4 or newer UniPhier SoCs.
 
 source "drivers/i2c/muxes/Kconfig"
+
+endmenu