On Tue, 21 Mar 2023, Kate Hsuan wrote:
> Add MFD cell for tps68470-led.
>
> Reviewed-by: Daniel Scally <dan.scally@xxxxxxxxxxxxxxxx>
> Signed-off-by: Kate Hsuan <hpa@xxxxxxxxxx>
> ---
> drivers/platform/x86/intel/int3472/tps68470.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/intel/int3472/tps68470.c b/drivers/platform/x86/intel/int3472/tps68470.c
> index 5b8d1a9620a5..82ef022f8916 100644
> --- a/drivers/platform/x86/intel/int3472/tps68470.c
> +++ b/drivers/platform/x86/intel/int3472/tps68470.c
> @@ -17,7 +17,7 @@
> #define DESIGNED_FOR_CHROMEOS 1
> #define DESIGNED_FOR_WINDOWS 2
>
> -#define TPS68470_WIN_MFD_CELL_COUNT 3
> +#define TPS68470_WIN_MFD_CELL_COUNT 4
>
> static const struct mfd_cell tps68470_cros[] = {
> { .name = "tps68470-gpio" },
> @@ -193,7 +193,8 @@ static int skl_int3472_tps68470_probe(struct i2c_client *client)
> cells[1].name = "tps68470-regulator";
> cells[1].platform_data = (void *)board_data->tps68470_regulator_pdata;
> cells[1].pdata_size = sizeof(struct tps68470_regulator_platform_data);
> - cells[2].name = "tps68470-gpio";
> + cells[2].name = "tps68470-led";
> + cells[3].name = "tps68470-gpio";
The question is, why is the MFD API being used out side of drivers/mfd?
> for (i = 0; i < board_data->n_gpiod_lookups; i++)
> gpiod_add_lookup_table(board_data->tps68470_gpio_lookup_tables[i]);
> --
> 2.39.2
>
--
Lee Jones [李琼斯]
