Re: [PATCH v16 4/8] mfd: p3h2x4x: Add driver for NXP P3H2x4x i3c hub and on-die regulator

From: Krzysztof Kozlowski

Date: Thu Aug 27 2026 - 06:04:24 EST


On 26/08/2026 12:38, Lakshay Piplani wrote:

> +
> +static const struct i3c_device_id p3h2x4x_i3c_ids[] = {
> + I3C_CLASS(I3C_DCR_HUB, NULL),
> + { /* sentinel */ },
> +};
> +MODULE_DEVICE_TABLE(i3c, p3h2x4x_i3c_ids);
> +
> +static const struct i2c_device_id p3h2x4x_i2c_id_table[] = {
> + { .name = "nxp-i3c-hub" },
> + { /* sentinel */ }
> +};
> +MODULE_DEVICE_TABLE(i2c, p3h2x4x_i2c_id_table);
> +
> +static const struct of_device_id p3h2x4x_i2c_of_match[] = {
> + { .compatible = "nxp,p3h2440", },
> + { .compatible = "nxp,p3h2441", },
> + { .compatible = "nxp,p3h2840", },
> + { .compatible = "nxp,p3h2841", },

So devices are fully compatible? Why isn't this expressed in the
binding? Or explained in the commit msg?


Best regards,
Krzysztof