RE: [EXT] Re: [PATCH v14 0/8] Add support for NXP P3H2x4x I3C hub driver

[Lakshay Piplani]

> -----Original Message-----
> From: Lee Jones <lee@xxxxxxxxxx>
> Sent: Thursday, July 23, 2026 6:01 PM
> To: Lakshay Piplani <lakshay.piplani@xxxxxxx>
> Cc: linux-kernel@xxxxxxxxxxxxxxx; linux-i3c@xxxxxxxxxxxxxxxxxxx;
> alexandre.belloni@xxxxxxxxxxx; krzk+dt@xxxxxxxxxx; robh@xxxxxxxxxx;
> conor+dt@xxxxxxxxxx; devicetree@xxxxxxxxxxxxxxx; broonie@xxxxxxxxxx; Frank
> Li <frank.li@xxxxxxx>; lgirdwood@xxxxxxxxx; Vikash Bansal
> <vikash.bansal@xxxxxxx>; Priyanka Jain <priyanka.jain@xxxxxxx>; Aman
> Kumar Pandey <aman.kumarpandey@xxxxxxx>
> Subject: [EXT] Re: [PATCH v14 0/8] Add support for NXP P3H2x4x I3C hub
> driver
> 
> Caution: This is an external email. Please take care when clicking links or
> opening attachments. When in doubt, report the message using the 'Report
> this email' button
> 
> 
> On Tue, 14 Jul 2026, Lakshay Piplani wrote:
> 
> > This is an MFD driver integrating I3C hub and on-die regulators.
> >
> > The series introduces:
> > - Core I3C master enhancements required for hub support
> > - Generic I3C hub framework
> > - MFD driver with regulator and I3C hub child drivers for the P3H2x4x
> > I3C hub
> >
> > Below patches from v11 have already been applied to i3c/next branch:
> >  - 79c41666b397 ("i3c: master: rename i3c_master_reattach_i3c_dev() to
> *_locked")
> >
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.
> >
> kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Fi3c%2Flinux.git%2Fco
> mm
> >
> it%2F%3Fid%3D79c41666b397&data=05%7C02%7Clakshay.piplani%40nxp.co
> m%7Cf
> >
> f46ce74164a4dc1ded008dee8b64a9e%7C686ea1d3bc2b4c6fa92cd99c5c3016
> 35%7C0
> > %7C0%7C639204066796167732%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0
> eU1hcGkiOnRy
> >
> dWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3
> D%
> >
> 3D%7C0%7C%7C%7C&sdata=aySk2IlbCKMrsbqTTdBcaBPT1JZ5uLMB4G5WGIu
> ZmOs%3D&r
> > eserved=0
> >  - 8d8afa428318 ("i3c: master: Expose the APIs to support I3C hub")
> >
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.
> >
> kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Fi3c%2Flinux.git%2Fco
> mm
> >
> it%2F%3Fid%3D8d8afa428318&data=05%7C02%7Clakshay.piplani%40nxp.co
> m%7Cf
> >
> f46ce74164a4dc1ded008dee8b64a9e%7C686ea1d3bc2b4c6fa92cd99c5c3016
> 35%7C0
> > %7C0%7C639204066796206521%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0
> eU1hcGkiOnRy
> >
> dWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3
> D%
> >
> 3D%7C0%7C%7C%7C&sdata=xbBVBGJ18l5zVn3c1TedINVaMmU%2BbCTeoApV
> DkkFkFY%3D
> > &reserved=0
> 
> Am I correct in thinking that the only deps are between the Regulator and MFD
> drivers?
> 
> --
> Lee Jones

The MFD parent driver is required by both the regulator driver and the P3H2x4x hub driver. The P3H2x4x I3C hub driver also requires the generic I3C hub core, which in turn depends on the I3C core changes referenced above.

I will make this complete dependency chain explicit in the v15 cover letter.