Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [PATCH v5 1/1] platform/x86/intel_cht_int33fe: Split code to USB
 Micro-B and Type-C variants
To:     Yauhen Kharuzhy <jekhor@gmail.com>,
        Darren Hart <dvhart@infradead.org>,
        platform-driver-x86@vger.kernel.org
Cc:     linux-kernel@vger.kernel.org, Andy Shevchenko <andy@infradead.org>
References: <20190920223356.6622-1-jekhor@gmail.com>
 <20190920223356.6622-2-jekhor@gmail.com>
From:   Hans de Goede <hdegoede@redhat.com>
Message-ID: <1cca117d-1951-0335-1aef-ac994c3c757b@redhat.com>
Date:   Sat, 21 Sep 2019 20:31:32 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.1.0
MIME-Version: 1.0
In-Reply-To: <20190920223356.6622-2-jekhor@gmail.com>
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi,

On 21-09-2019 00:33, Yauhen Kharuzhy wrote:
> Existing intel_cht_int33fe ACPI pseudo-device driver assumes that
> hardware has Type-C connector and register related devices described as
> I2C connections in the _CRS resource.
>=20
> There is at least one hardware (Lenovo Yoga Book YB1-91L/F) with Micro-B
> USB connector exists. It has INT33FE device in the DSDT table but
> there are only two I2C connection described: PMIC and BQ27452 battery
> fuel gauge.
>=20
> Splitting existing INT33FE driver allow to maintain code for USB Micro-B
> (or AB) connector variant separately and make it simpler.
>=20
> Split driver to intel_cht_int33fe_common.c and
> intel_cht_int33fe_{microb,typec}.c. Compile all this sources to one .ko
> module to make user experience easier.
>=20
> Signed-off-by: Yauhen Kharuzhy <jekhor@gmail.com>

This version still works for me on my typec device:

Tested-by: Hans de Goede <hdegoede@redhat.com>

The code also looks good to me:

Reviewed-by: Hans de Goede <hdegoede@redhat.com>

Regards,

Hans


> ---
>   drivers/platform/x86/Kconfig                  |  10 +-
>   drivers/platform/x86/Makefile                 |   4 +
>   .../platform/x86/intel_cht_int33fe_common.c   | 147 ++++++++++++++++++
>   .../platform/x86/intel_cht_int33fe_common.h   |  41 +++++
>   .../platform/x86/intel_cht_int33fe_microb.c   |  57 +++++++
>   ...ht_int33fe.c =3D> intel_cht_int33fe_typec.c} |  78 +---------
>   6 files changed, 265 insertions(+), 72 deletions(-)
>   create mode 100644 drivers/platform/x86/intel_cht_int33fe_common.c
>   create mode 100644 drivers/platform/x86/intel_cht_int33fe_common.h
>   create mode 100644 drivers/platform/x86/intel_cht_int33fe_microb.c
>   rename drivers/platform/x86/{intel_cht_int33fe.c =3D> intel_cht_int33fe=
_typec.c} (82%)
>=20
> diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig
> index 1b67bb578f9f..e9e5aa791caf 100644
> --- a/drivers/platform/x86/Kconfig
> +++ b/drivers/platform/x86/Kconfig
> @@ -930,14 +930,20 @@ config INTEL_CHT_INT33FE
>   =09  This driver add support for the INT33FE ACPI device found on
>   =09  some Intel Cherry Trail devices.
>  =20
> +=09  There are two kinds of INT33FE ACPI device possible: for hardware
> +=09  with USB Type-C and Micro-B connectors. This driver supports both.
> +
>   =09  The INT33FE ACPI device has a CRS table with I2cSerialBusV2
> -=09  resources for 3 devices: Maxim MAX17047 Fuel Gauge Controller,
> +=09  resources for Fuel Gauge Controller and (in the Type-C variant)
>   =09  FUSB302 USB Type-C Controller and PI3USB30532 USB switch.
>   =09  This driver instantiates i2c-clients for these, so that standard
>   =09  i2c drivers for these chips can bind to the them.
>  =20
>   =09  If you enable this driver it is advised to also select
> -=09  CONFIG_TYPEC_FUSB302=3Dm and CONFIG_BATTERY_MAX17042=3Dm.
> +=09  CONFIG_BATTERY_BQ27XXX=3Dm or CONFIG_BATTERY_BQ27XXX_I2C=3Dm for Mi=
cro-B
> +=09  device and CONFIG_TYPEC_FUSB302=3Dm and CONFIG_BATTERY_MAX17042=3Dm
> +=09  for Type-C device.
> +
>  =20
>   config INTEL_INT0002_VGPIO
>   =09tristate "Intel ACPI INT0002 Virtual GPIO driver"
> diff --git a/drivers/platform/x86/Makefile b/drivers/platform/x86/Makefil=
e
> index 415104033060..216d3b6fd6a7 100644
> --- a/drivers/platform/x86/Makefile
> +++ b/drivers/platform/x86/Makefile
> @@ -61,6 +61,10 @@ obj-$(CONFIG_TOSHIBA_BT_RFKILL)=09+=3D toshiba_bluetoo=
th.o
>   obj-$(CONFIG_TOSHIBA_HAPS)=09+=3D toshiba_haps.o
>   obj-$(CONFIG_TOSHIBA_WMI)=09+=3D toshiba-wmi.o
>   obj-$(CONFIG_INTEL_CHT_INT33FE)=09+=3D intel_cht_int33fe.o
> +intel_cht_int33fe-objs=09=09:=3D intel_cht_int33fe_common.o \
> +=09=09=09=09   intel_cht_int33fe_typec.o \
> +=09=09=09=09   intel_cht_int33fe_microb.o
> +
>   obj-$(CONFIG_INTEL_INT0002_VGPIO) +=3D intel_int0002_vgpio.o
>   obj-$(CONFIG_INTEL_HID_EVENT)=09+=3D intel-hid.o
>   obj-$(CONFIG_INTEL_VBTN)=09+=3D intel-vbtn.o
> diff --git a/drivers/platform/x86/intel_cht_int33fe_common.c b/drivers/pl=
atform/x86/intel_cht_int33fe_common.c
> new file mode 100644
> index 000000000000..42dd11623f56
> --- /dev/null
> +++ b/drivers/platform/x86/intel_cht_int33fe_common.c
> @@ -0,0 +1,147 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Common code for Intel Cherry Trail ACPI INT33FE pseudo device drivers
> + * (USB Micro-B and Type-C connector variants).
> + *
> + * Copyright (c) 2019 Yauhen Kharuzhy <jekhor@gmail.com>
> + */
> +
> +#include <linux/acpi.h>
> +#include <linux/i2c.h>
> +#include <linux/module.h>
> +#include <linux/platform_device.h>
> +#include <linux/slab.h>
> +
> +#include "intel_cht_int33fe_common.h"
> +
> +#define EXPECTED_PTYPE=09=094
> +
> +static int cht_int33fe_i2c_res_filter(struct acpi_resource *ares, void *=
data)
> +{
> +=09struct acpi_resource_i2c_serialbus *sb;
> +=09int *count =3D data;
> +
> +=09if (i2c_acpi_get_i2c_resource(ares, &sb))
> +=09=09(*count)++;
> +
> +=09return 1;
> +}
> +
> +static int cht_int33fe_count_i2c_clients(struct device *dev)
> +{
> +=09struct acpi_device *adev;
> +=09LIST_HEAD(resource_list);
> +=09int count =3D 0;
> +
> +=09adev =3D ACPI_COMPANION(dev);
> +=09if (!adev)
> +=09=09return -EINVAL;
> +
> +=09acpi_dev_get_resources(adev, &resource_list,
> +=09=09=09       cht_int33fe_i2c_res_filter, &count);
> +
> +=09acpi_dev_free_resource_list(&resource_list);
> +
> +=09return count;
> +}
> +
> +static int cht_int33fe_check_hw_type(struct device *dev)
> +{
> +=09unsigned long long ptyp;
> +=09acpi_status status;
> +=09int ret;
> +
> +=09status =3D acpi_evaluate_integer(ACPI_HANDLE(dev), "PTYP", NULL, &pty=
p);
> +=09if (ACPI_FAILURE(status)) {
> +=09=09dev_err(dev, "Error getting PTYPE\n");
> +=09=09return -ENODEV;
> +=09}
> +
> +=09/*
> +=09 * The same ACPI HID is used for different configurations check PTYP
> +=09 * to ensure that we are dealing with the expected config.
> +=09 */
> +=09if (ptyp !=3D EXPECTED_PTYPE)
> +=09=09return -ENODEV;
> +
> +=09/* Check presence of INT34D3 (hardware-rev 3) expected for ptype =3D=
=3D 4 */
> +=09if (!acpi_dev_present("INT34D3", "1", 3)) {
> +=09=09dev_err(dev, "Error PTYPE =3D=3D %d, but no INT34D3 device\n",
> +=09=09=09EXPECTED_PTYPE);
> +=09=09return -ENODEV;
> +=09}
> +
> +=09ret =3D cht_int33fe_count_i2c_clients(dev);
> +=09if (ret < 0)
> +=09=09return ret;
> +
> +=09switch (ret) {
> +=09case 2:
> +=09=09return INT33FE_HW_MICROB;
> +=09case 4:
> +=09=09return INT33FE_HW_TYPEC;
> +=09default:
> +=09=09return -ENODEV;
> +=09}
> +}
> +
> +static int cht_int33fe_probe(struct platform_device *pdev)
> +{
> +=09struct cht_int33fe_data *data;
> +=09struct device *dev =3D &pdev->dev;
> +=09int ret;
> +
> +=09ret =3D cht_int33fe_check_hw_type(dev);
> +=09if (ret < 0)
> +=09=09return ret;
> +
> +=09data =3D devm_kzalloc(dev, sizeof(*data), GFP_KERNEL);
> +=09if (!data)
> +=09=09return -ENOMEM;
> +
> +=09data->dev =3D dev;
> +
> +=09switch (ret) {
> +=09case INT33FE_HW_MICROB:
> +=09=09data->probe =3D cht_int33fe_microb_probe;
> +=09=09data->remove =3D cht_int33fe_microb_remove;
> +=09=09break;
> +
> +=09case INT33FE_HW_TYPEC:
> +=09=09data->probe =3D cht_int33fe_typec_probe;
> +=09=09data->remove =3D cht_int33fe_typec_remove;
> +=09=09break;
> +=09}
> +
> +=09platform_set_drvdata(pdev, data);
> +
> +=09return data->probe(data);
> +}
> +
> +static int cht_int33fe_remove(struct platform_device *pdev)
> +{
> +=09struct cht_int33fe_data *data =3D platform_get_drvdata(pdev);
> +
> +=09return data->remove(data);
> +}
> +
> +static const struct acpi_device_id cht_int33fe_acpi_ids[] =3D {
> +=09{ "INT33FE", },
> +=09{ }
> +};
> +MODULE_DEVICE_TABLE(acpi, cht_int33fe_acpi_ids);
> +
> +static struct platform_driver cht_int33fe_driver =3D {
> +=09.driver=09=3D {
> +=09=09.name =3D "Intel Cherry Trail ACPI INT33FE driver",
> +=09=09.acpi_match_table =3D ACPI_PTR(cht_int33fe_acpi_ids),
> +=09},
> +=09.probe =3D cht_int33fe_probe,
> +=09.remove =3D cht_int33fe_remove,
> +};
> +
> +module_platform_driver(cht_int33fe_driver);
> +
> +MODULE_DESCRIPTION("Intel Cherry Trail ACPI INT33FE pseudo device driver=
");
> +MODULE_AUTHOR("Yauhen Kharuzhy <jekhor@gmail.com>");
> +MODULE_LICENSE("GPL v2");
> diff --git a/drivers/platform/x86/intel_cht_int33fe_common.h b/drivers/pl=
atform/x86/intel_cht_int33fe_common.h
> new file mode 100644
> index 000000000000..03cd45f4e8cb
> --- /dev/null
> +++ b/drivers/platform/x86/intel_cht_int33fe_common.h
> @@ -0,0 +1,41 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +/*
> + * Common code for Intel Cherry Trail ACPI INT33FE pseudo device drivers
> + * (USB Micro-B and Type-C connector variants), header file
> + *
> + * Copyright (c) 2019 Yauhen Kharuzhy <jekhor@gmail.com>
> + */
> +
> +#ifndef _INTEL_CHT_INT33FE_COMMON_H
> +#define _INTEL_CHT_INT33FE_COMMON_H
> +
> +#include <linux/device.h>
> +#include <linux/fwnode.h>
> +#include <linux/i2c.h>
> +
> +enum int33fe_hw_type {
> +=09INT33FE_HW_MICROB,
> +=09INT33FE_HW_TYPEC,
> +};
> +
> +struct cht_int33fe_data {
> +=09struct device *dev;
> +
> +=09int (*probe)(struct cht_int33fe_data *data);
> +=09int (*remove)(struct cht_int33fe_data *data);
> +
> +=09struct i2c_client *battery_fg;
> +
> +=09/* Type-C only */
> +=09struct i2c_client *fusb302;
> +=09struct i2c_client *pi3usb30532;
> +
> +=09struct fwnode_handle *dp;
> +};
> +
> +int cht_int33fe_microb_probe(struct cht_int33fe_data *data);
> +int cht_int33fe_microb_remove(struct cht_int33fe_data *data);
> +int cht_int33fe_typec_probe(struct cht_int33fe_data *data);
> +int cht_int33fe_typec_remove(struct cht_int33fe_data *data);
> +
> +#endif /* _INTEL_CHT_INT33FE_COMMON_H */
> diff --git a/drivers/platform/x86/intel_cht_int33fe_microb.c b/drivers/pl=
atform/x86/intel_cht_int33fe_microb.c
> new file mode 100644
> index 000000000000..20b11e0d9a75
> --- /dev/null
> +++ b/drivers/platform/x86/intel_cht_int33fe_microb.c
> @@ -0,0 +1,57 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Intel Cherry Trail ACPI INT33FE pseudo device driver for devices with
> + * USB Micro-B connector (e.g. without of FUSB302 USB Type-C controller)
> + *
> + * Copyright (C) 2019 Yauhen Kharuzhy <jekhor@gmail.com>
> + *
> + * At least one Intel Cherry Trail based device which ship with Windows =
10
> + * (Lenovo YogaBook YB1-X91L/F tablet), have this weird INT33FE ACPI dev=
ice
> + * with a CRS table with 2 I2cSerialBusV2 resources, for 2 different chi=
ps
> + * attached to various i2c busses:
> + * 1. The Whiskey Cove PMIC, which is also described by the INT34D3 ACPI=
 device
> + * 2. TI BQ27542 Fuel Gauge Controller
> + *
> + * So this driver is a stub / pseudo driver whose only purpose is to
> + * instantiate i2c-client for battery fuel gauge, so that standard i2c d=
river
> + * for these chip can bind to the it.
> + */
> +
> +#include <linux/acpi.h>
> +#include <linux/i2c.h>
> +#include <linux/module.h>
> +#include <linux/pci.h>
> +#include <linux/platform_device.h>
> +#include <linux/regulator/consumer.h>
> +#include <linux/slab.h>
> +#include <linux/usb/pd.h>
> +
> +#include "intel_cht_int33fe_common.h"
> +
> +static const char * const bq27xxx_suppliers[] =3D { "bq25890-charger" };
> +
> +static const struct property_entry bq27xxx_props[] =3D {
> +=09PROPERTY_ENTRY_STRING_ARRAY("supplied-from", bq27xxx_suppliers),
> +=09{ }
> +};
> +
> +int cht_int33fe_microb_probe(struct cht_int33fe_data *data)
> +{
> +=09struct device *dev =3D data->dev;
> +=09struct i2c_board_info board_info;
> +
> +=09memset(&board_info, 0, sizeof(board_info));
> +=09strscpy(board_info.type, "bq27542", ARRAY_SIZE(board_info.type));
> +=09board_info.dev_name =3D "bq27542";
> +=09board_info.properties =3D bq27xxx_props;
> +=09data->battery_fg =3D i2c_acpi_new_device(dev, 1, &board_info);
> +
> +=09return PTR_ERR_OR_ZERO(data->battery_fg);
> +}
> +
> +int cht_int33fe_microb_remove(struct cht_int33fe_data *data)
> +{
> +=09i2c_unregister_device(data->battery_fg);
> +
> +=09return 0;
> +}
> diff --git a/drivers/platform/x86/intel_cht_int33fe.c b/drivers/platform/=
x86/intel_cht_int33fe_typec.c
> similarity index 82%
> rename from drivers/platform/x86/intel_cht_int33fe.c
> rename to drivers/platform/x86/intel_cht_int33fe_typec.c
> index 1d5d877b9582..2d097fc2dd46 100644
> --- a/drivers/platform/x86/intel_cht_int33fe.c
> +++ b/drivers/platform/x86/intel_cht_int33fe_typec.c
> @@ -17,17 +17,15 @@
>    * for these chips can bind to the them.
>    */
>  =20
> -#include <linux/acpi.h>
>   #include <linux/i2c.h>
>   #include <linux/interrupt.h>
> -#include <linux/module.h>
>   #include <linux/pci.h>
>   #include <linux/platform_device.h>
>   #include <linux/regulator/consumer.h>
>   #include <linux/slab.h>
>   #include <linux/usb/pd.h>
>  =20
> -#define EXPECTED_PTYPE=09=094
> +#include "intel_cht_int33fe_common.h"
>  =20
>   enum {
>   =09INT33FE_NODE_FUSB302,
> @@ -38,14 +36,6 @@ enum {
>   =09INT33FE_NODE_MAX,
>   };
>  =20
> -struct cht_int33fe_data {
> -=09struct i2c_client *max17047;
> -=09struct i2c_client *fusb302;
> -=09struct i2c_client *pi3usb30532;
> -
> -=09struct fwnode_handle *dp;
> -};
> -
>   static const struct software_node nodes[];
>  =20
>   static const struct software_node_ref_args pi3usb30532_ref =3D {
> @@ -251,43 +241,20 @@ cht_int33fe_register_max17047(struct device *dev, s=
truct cht_int33fe_data *data)
>   =09strlcpy(board_info.type, "max17047", I2C_NAME_SIZE);
>   =09board_info.dev_name =3D "max17047";
>   =09board_info.fwnode =3D fwnode;
> -=09data->max17047 =3D i2c_acpi_new_device(dev, 1, &board_info);
> +=09data->battery_fg =3D i2c_acpi_new_device(dev, 1, &board_info);
>  =20
> -=09return PTR_ERR_OR_ZERO(data->max17047);
> +=09return PTR_ERR_OR_ZERO(data->battery_fg);
>   }
>  =20
> -static int cht_int33fe_probe(struct platform_device *pdev)
> +int cht_int33fe_typec_probe(struct cht_int33fe_data *data)
>   {
> -=09struct device *dev =3D &pdev->dev;
> +=09struct device *dev =3D data->dev;
>   =09struct i2c_board_info board_info;
> -=09struct cht_int33fe_data *data;
>   =09struct fwnode_handle *fwnode;
>   =09struct regulator *regulator;
> -=09unsigned long long ptyp;
> -=09acpi_status status;
>   =09int fusb302_irq;
>   =09int ret;
>  =20
> -=09status =3D acpi_evaluate_integer(ACPI_HANDLE(dev), "PTYP", NULL, &pty=
p);
> -=09if (ACPI_FAILURE(status)) {
> -=09=09dev_err(dev, "Error getting PTYPE\n");
> -=09=09return -ENODEV;
> -=09}
> -
> -=09/*
> -=09 * The same ACPI HID is used for different configurations check PTYP
> -=09 * to ensure that we are dealing with the expected config.
> -=09 */
> -=09if (ptyp !=3D EXPECTED_PTYPE)
> -=09=09return -ENODEV;
> -
> -=09/* Check presence of INT34D3 (hardware-rev 3) expected for ptype =3D=
=3D 4 */
> -=09if (!acpi_dev_present("INT34D3", "1", 3)) {
> -=09=09dev_err(dev, "Error PTYPE =3D=3D %d, but no INT34D3 device\n",
> -=09=09=09EXPECTED_PTYPE);
> -=09=09return -ENODEV;
> -=09}
> -
>   =09/*
>   =09 * We expect the WC PMIC to be paired with a TI bq24292i charger-IC.
>   =09 * We check for the bq24292i vbus regulator here, this has 2 purpose=
s:
> @@ -317,10 +284,6 @@ static int cht_int33fe_probe(struct platform_device =
*pdev)
>   =09=09return fusb302_irq;
>   =09}
>  =20
> -=09data =3D devm_kzalloc(dev, sizeof(*data), GFP_KERNEL);
> -=09if (!data)
> -=09=09return -ENOMEM;
> -
>   =09ret =3D cht_int33fe_add_nodes(data);
>   =09if (ret)
>   =09=09return ret;
> @@ -365,15 +328,13 @@ static int cht_int33fe_probe(struct platform_device=
 *pdev)
>   =09=09goto out_unregister_fusb302;
>   =09}
>  =20
> -=09platform_set_drvdata(pdev, data);
> -
>   =09return 0;
>  =20
>   out_unregister_fusb302:
>   =09i2c_unregister_device(data->fusb302);
>  =20
>   out_unregister_max17047:
> -=09i2c_unregister_device(data->max17047);
> +=09i2c_unregister_device(data->battery_fg);
>  =20
>   out_remove_nodes:
>   =09cht_int33fe_remove_nodes(data);
> @@ -381,36 +342,13 @@ static int cht_int33fe_probe(struct platform_device=
 *pdev)
>   =09return ret;
>   }
>  =20
> -static int cht_int33fe_remove(struct platform_device *pdev)
> +int cht_int33fe_typec_remove(struct cht_int33fe_data *data)
>   {
> -=09struct cht_int33fe_data *data =3D platform_get_drvdata(pdev);
> -
>   =09i2c_unregister_device(data->pi3usb30532);
>   =09i2c_unregister_device(data->fusb302);
> -=09i2c_unregister_device(data->max17047);
> +=09i2c_unregister_device(data->battery_fg);
>  =20
>   =09cht_int33fe_remove_nodes(data);
>  =20
>   =09return 0;
>   }
> -
> -static const struct acpi_device_id cht_int33fe_acpi_ids[] =3D {
> -=09{ "INT33FE", },
> -=09{ }
> -};
> -MODULE_DEVICE_TABLE(acpi, cht_int33fe_acpi_ids);
> -
> -static struct platform_driver cht_int33fe_driver =3D {
> -=09.driver=09=3D {
> -=09=09.name =3D "Intel Cherry Trail ACPI INT33FE driver",
> -=09=09.acpi_match_table =3D ACPI_PTR(cht_int33fe_acpi_ids),
> -=09},
> -=09.probe =3D cht_int33fe_probe,
> -=09.remove =3D cht_int33fe_remove,
> -};
> -
> -module_platform_driver(cht_int33fe_driver);
> -
> -MODULE_DESCRIPTION("Intel Cherry Trail ACPI INT33FE pseudo device driver=
");
> -MODULE_AUTHOR("Hans de Goede <hdegoede@redhat.com>");
> -MODULE_LICENSE("GPL v2");
>=20