intel_cht_int33fe.c 7.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257
  1. // SPDX-License-Identifier: GPL-2.0
  2. /*
  3. * Intel Cherry Trail ACPI INT33FE pseudo device driver
  4. *
  5. * Copyright (C) 2017 Hans de Goede <hdegoede@redhat.com>
  6. *
  7. * Some Intel Cherry Trail based device which ship with Windows 10, have
  8. * this weird INT33FE ACPI device with a CRS table with 4 I2cSerialBusV2
  9. * resources, for 4 different chips attached to various i2c busses:
  10. * 1. The Whiskey Cove pmic, which is also described by the INT34D3 ACPI device
  11. * 2. Maxim MAX17047 Fuel Gauge Controller
  12. * 3. FUSB302 USB Type-C Controller
  13. * 4. PI3USB30532 USB switch
  14. *
  15. * So this driver is a stub / pseudo driver whose only purpose is to
  16. * instantiate i2c-clients for chips 2 - 4, so that standard i2c drivers
  17. * for these chips can bind to the them.
  18. */
  19. #include <linux/acpi.h>
  20. #include <linux/i2c.h>
  21. #include <linux/interrupt.h>
  22. #include <linux/module.h>
  23. #include <linux/platform_device.h>
  24. #include <linux/regulator/consumer.h>
  25. #include <linux/slab.h>
  26. #define EXPECTED_PTYPE 4
  27. struct cht_int33fe_data {
  28. struct i2c_client *max17047;
  29. struct i2c_client *fusb302;
  30. struct i2c_client *pi3usb30532;
  31. /* Contain a list-head must be per device */
  32. struct device_connection connections[5];
  33. };
  34. /*
  35. * Grrr I severly dislike buggy BIOS-es. At least one BIOS enumerates
  36. * the max17047 both through the INT33FE ACPI device (it is right there
  37. * in the resources table) as well as through a separate MAX17047 device.
  38. *
  39. * These helpers are used to work around this by checking if an i2c-client
  40. * for the max17047 has already been registered.
  41. */
  42. static int cht_int33fe_check_for_max17047(struct device *dev, void *data)
  43. {
  44. struct i2c_client **max17047 = data;
  45. struct acpi_device *adev;
  46. const char *hid;
  47. adev = ACPI_COMPANION(dev);
  48. if (!adev)
  49. return 0;
  50. hid = acpi_device_hid(adev);
  51. /* The MAX17047 ACPI node doesn't have an UID, so we don't check that */
  52. if (strcmp(hid, "MAX17047"))
  53. return 0;
  54. *max17047 = to_i2c_client(dev);
  55. return 1;
  56. }
  57. static struct i2c_client *cht_int33fe_find_max17047(void)
  58. {
  59. struct i2c_client *max17047 = NULL;
  60. i2c_for_each_dev(&max17047, cht_int33fe_check_for_max17047);
  61. return max17047;
  62. }
  63. static const char * const max17047_suppliers[] = { "bq24190-charger" };
  64. static const struct property_entry max17047_props[] = {
  65. PROPERTY_ENTRY_STRING_ARRAY("supplied-from", max17047_suppliers),
  66. { }
  67. };
  68. static const struct property_entry fusb302_props[] = {
  69. PROPERTY_ENTRY_STRING("fcs,extcon-name", "cht_wcove_pwrsrc"),
  70. PROPERTY_ENTRY_U32("fcs,max-sink-microvolt", 12000000),
  71. PROPERTY_ENTRY_U32("fcs,max-sink-microamp", 3000000),
  72. PROPERTY_ENTRY_U32("fcs,max-sink-microwatt", 36000000),
  73. { }
  74. };
  75. static int cht_int33fe_probe(struct platform_device *pdev)
  76. {
  77. struct device *dev = &pdev->dev;
  78. struct i2c_board_info board_info;
  79. struct cht_int33fe_data *data;
  80. struct i2c_client *max17047;
  81. struct regulator *regulator;
  82. unsigned long long ptyp;
  83. acpi_status status;
  84. int fusb302_irq;
  85. int ret;
  86. status = acpi_evaluate_integer(ACPI_HANDLE(dev), "PTYP", NULL, &ptyp);
  87. if (ACPI_FAILURE(status)) {
  88. dev_err(dev, "Error getting PTYPE\n");
  89. return -ENODEV;
  90. }
  91. /*
  92. * The same ACPI HID is used for different configurations check PTYP
  93. * to ensure that we are dealing with the expected config.
  94. */
  95. if (ptyp != EXPECTED_PTYPE)
  96. return -ENODEV;
  97. /* Check presence of INT34D3 (hardware-rev 3) expected for ptype == 4 */
  98. if (!acpi_dev_present("INT34D3", "1", 3)) {
  99. dev_err(dev, "Error PTYPE == %d, but no INT34D3 device\n",
  100. EXPECTED_PTYPE);
  101. return -ENODEV;
  102. }
  103. /*
  104. * We expect the WC PMIC to be paired with a TI bq24292i charger-IC.
  105. * We check for the bq24292i vbus regulator here, this has 2 purposes:
  106. * 1) The bq24292i allows charging with up to 12V, setting the fusb302's
  107. * max-snk voltage to 12V with another charger-IC is not good.
  108. * 2) For the fusb302 driver to get the bq24292i vbus regulator, the
  109. * regulator-map, which is part of the bq24292i regulator_init_data,
  110. * must be registered before the fusb302 is instantiated, otherwise
  111. * it will end up with a dummy-regulator.
  112. * Note "cht_wc_usb_typec_vbus" comes from the regulator_init_data
  113. * which is defined in i2c-cht-wc.c from where the bq24292i i2c-client
  114. * gets instantiated. We use regulator_get_optional here so that we
  115. * don't end up getting a dummy-regulator ourselves.
  116. */
  117. regulator = regulator_get_optional(dev, "cht_wc_usb_typec_vbus");
  118. if (IS_ERR(regulator)) {
  119. ret = PTR_ERR(regulator);
  120. return (ret == -ENODEV) ? -EPROBE_DEFER : ret;
  121. }
  122. regulator_put(regulator);
  123. /* The FUSB302 uses the irq at index 1 and is the only irq user */
  124. fusb302_irq = acpi_dev_gpio_irq_get(ACPI_COMPANION(dev), 1);
  125. if (fusb302_irq < 0) {
  126. if (fusb302_irq != -EPROBE_DEFER)
  127. dev_err(dev, "Error getting FUSB302 irq\n");
  128. return fusb302_irq;
  129. }
  130. data = devm_kzalloc(dev, sizeof(*data), GFP_KERNEL);
  131. if (!data)
  132. return -ENOMEM;
  133. /* Work around BIOS bug, see comment on cht_int33fe_find_max17047 */
  134. max17047 = cht_int33fe_find_max17047();
  135. if (max17047) {
  136. /* Pre-existing i2c-client for the max17047, add device-props */
  137. ret = device_add_properties(&max17047->dev, max17047_props);
  138. if (ret)
  139. return ret;
  140. /* And re-probe to get the new device-props applied. */
  141. ret = device_reprobe(&max17047->dev);
  142. if (ret)
  143. dev_warn(dev, "Reprobing max17047 error: %d\n", ret);
  144. } else {
  145. memset(&board_info, 0, sizeof(board_info));
  146. strlcpy(board_info.type, "max17047", I2C_NAME_SIZE);
  147. board_info.dev_name = "max17047";
  148. board_info.properties = max17047_props;
  149. data->max17047 = i2c_acpi_new_device(dev, 1, &board_info);
  150. if (!data->max17047)
  151. return -EPROBE_DEFER; /* Wait for i2c-adapter to load */
  152. }
  153. data->connections[0].endpoint[0] = "port0";
  154. data->connections[0].endpoint[1] = "i2c-pi3usb30532";
  155. data->connections[0].id = "typec-switch";
  156. data->connections[1].endpoint[0] = "port0";
  157. data->connections[1].endpoint[1] = "i2c-pi3usb30532";
  158. data->connections[1].id = "typec-mux";
  159. data->connections[2].endpoint[0] = "port0";
  160. data->connections[2].endpoint[1] = "i2c-pi3usb30532";
  161. data->connections[2].id = "idff01m01";
  162. data->connections[3].endpoint[0] = "i2c-fusb302";
  163. data->connections[3].endpoint[1] = "intel_xhci_usb_sw-role-switch";
  164. data->connections[3].id = "usb-role-switch";
  165. device_connections_add(data->connections);
  166. memset(&board_info, 0, sizeof(board_info));
  167. strlcpy(board_info.type, "typec_fusb302", I2C_NAME_SIZE);
  168. board_info.dev_name = "fusb302";
  169. board_info.properties = fusb302_props;
  170. board_info.irq = fusb302_irq;
  171. data->fusb302 = i2c_acpi_new_device(dev, 2, &board_info);
  172. if (!data->fusb302)
  173. goto out_unregister_max17047;
  174. memset(&board_info, 0, sizeof(board_info));
  175. board_info.dev_name = "pi3usb30532";
  176. strlcpy(board_info.type, "pi3usb30532", I2C_NAME_SIZE);
  177. data->pi3usb30532 = i2c_acpi_new_device(dev, 3, &board_info);
  178. if (!data->pi3usb30532)
  179. goto out_unregister_fusb302;
  180. platform_set_drvdata(pdev, data);
  181. return 0;
  182. out_unregister_fusb302:
  183. i2c_unregister_device(data->fusb302);
  184. out_unregister_max17047:
  185. if (data->max17047)
  186. i2c_unregister_device(data->max17047);
  187. device_connections_remove(data->connections);
  188. return -EPROBE_DEFER; /* Wait for the i2c-adapter to load */
  189. }
  190. static int cht_int33fe_remove(struct platform_device *pdev)
  191. {
  192. struct cht_int33fe_data *data = platform_get_drvdata(pdev);
  193. i2c_unregister_device(data->pi3usb30532);
  194. i2c_unregister_device(data->fusb302);
  195. if (data->max17047)
  196. i2c_unregister_device(data->max17047);
  197. device_connections_remove(data->connections);
  198. return 0;
  199. }
  200. static const struct acpi_device_id cht_int33fe_acpi_ids[] = {
  201. { "INT33FE", },
  202. { }
  203. };
  204. MODULE_DEVICE_TABLE(acpi, cht_int33fe_acpi_ids);
  205. static struct platform_driver cht_int33fe_driver = {
  206. .driver = {
  207. .name = "Intel Cherry Trail ACPI INT33FE driver",
  208. .acpi_match_table = ACPI_PTR(cht_int33fe_acpi_ids),
  209. },
  210. .probe = cht_int33fe_probe,
  211. .remove = cht_int33fe_remove,
  212. };
  213. module_platform_driver(cht_int33fe_driver);
  214. MODULE_DESCRIPTION("Intel Cherry Trail ACPI INT33FE pseudo device driver");
  215. MODULE_AUTHOR("Hans de Goede <hdegoede@redhat.com>");
  216. MODULE_LICENSE("GPL v2");