Message ID | 20250116223915.430263-1-s-ramamoorthy@ti.com |
---|---|
Headers | show |
Series | Add TI TPS65214 PMIC MFD Support | expand |
On 16/01/2025 23:39, Shree Ramamoorthy wrote: > Use chip ID and chip_data struct to differentiate between 3 PMIC devices in > probe(). Add TPS65214 resource information. Update descriptions and > copyright information to reflect the driver supports 3 PMIC devices. > > Signed-off-by: Shree Ramamoorthy <s-ramamoorthy@ti.com> > --- > static struct tps65219_chip_data chip_info_table[] = { > + [TPS65214] = { > + .irq_chip = &tps65214_irq_chip, > + .cells = tps65214_cells, > + .n_cells = ARRAY_SIZE(tps65214_cells), > + }, > [TPS65215] = { > .irq_chip = &tps65215_irq_chip, > .cells = tps65215_cells, > @@ -421,6 +542,7 @@ static int tps65219_probe(struct i2c_client *client) > } > > static const struct of_device_id of_tps65219_match_table[] = { > + { .compatible = "ti,tps65214", .data = (void *)TPS65214, }, Where is the binding patch? It cannot be sent separately. > { .compatible = "ti,tps65215", .data = (void *)TPS65215, }, > { .compatible = "ti,tps65219", .data = (void *)TPS65219, }, Best regards, Krzysztof
On 16/01/2025 23:39, Shree Ramamoorthy wrote: > TPS65214 is a Power Management Integrated Circuit (PMIC) that has > significant register map overlap with TPS65215 and TPS65219. The series > introduces TPS65214 and adds the device to the multi-PMIC support driver. > > This follow-up series is dependent on: > Commit d23b7176df4a ("regulator: dt-bindings: Add TI TPS65214 PMIC bindings") What is this commit? Which tree? Recent next does not have it. The other thread said it depends on this patch, so how do you see it being merged? A depends on B, B depends on A. If A gets merged first: broken kernel. If B gets merged first: broken kernel? So what does this dependency and commit even mean? Best regards, Krzysztof