Devicetree
 help / color / mirror / Atom feed
From: Lakshay Piplani <lakshay.piplani@nxp.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>,
	"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"robh@kernel.org" <robh@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"lee@kernel.org" <lee@kernel.org>, Frank Li <frank.li@nxp.com>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>
Cc: Vikash Bansal <vikash.bansal@nxp.com>,
	Priyanka Jain <priyanka.jain@nxp.com>,
	Aman Kumar Pandey <aman.kumarpandey@nxp.com>
Subject: RE: [EXT] Re: [PATCH v18 3/8] dt-bindings: i3c: Add NXP P3H2x4x i3c-hub support
Date: Fri, 11 Sep 2026 09:22:35 +0000	[thread overview]
Message-ID: <AS4PR04MB936261B25BA49E704DF2BD14FBBE2@AS4PR04MB9362.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <AS4PR04MB93623E44246D2F29684491D6FBB02@AS4PR04MB9362.eurprd04.prod.outlook.com>

Hi Krzysztof,

A gentle follow-up on my previous reply. Could you please confirm whether
my understanding is correct before I prepare the next revision.

Regards,
Lakshay


NXP Public
> -----Original Message-----
> From: Lakshay Piplani
> Sent: Wednesday, September 9, 2026 2:03 PM
> To: 'Krzysztof Kozlowski' <krzk@kernel.org>; linux-kernel@vger.kernel.org;
> linux-i3c@lists.infradead.org; alexandre.belloni@bootlin.com;
> krzk+dt@kernel.org; robh@kernel.org; conor+dt@kernel.org;
> devicetree@vger.kernel.org; broonie@kernel.org; lee@kernel.org; Frank Li
> <frank.li@nxp.com>; lgirdwood@gmail.com
> Cc: Vikash Bansal <vikash.bansal@nxp.com>; Priyanka Jain
> <priyanka.jain@nxp.com>; Aman Kumar Pandey
> <aman.kumarpandey@nxp.com>
> Subject: RE: [EXT] Re: [PATCH v18 3/8] dt-bindings: i3c: Add NXP P3H2x4x i3c-
> hub support
>
> > >>> +
> > >>> +properties:
> > >>> +  compatible:
> > >>> +    enum:
> > >>> +      - nxp,p3h2440
> > >>> +      - nxp,p3h2441
> > >>> +      - nxp,p3h2840
> > >>> +      - nxp,p3h2841
> > >>
> > >> I don't see improvements.
> > >>
> > >
> > > For this one, could you let me know in a little bit more detail what
> > > you have
> > in mind?
> >
> > I questioned if devices are compatible. It seems the answer was that
> > yes. See writing bindings doc. There is plenty of examples showing how
> > to express compatibility, if they are compatible.
> >
>
> Thanks, understood.
>
> The variants share the same programming interface, so I'll express this through
> fallback compatibles with nxp,p3h2840 as the base compatible, e.g.
> compatible = "nxp,p3h2441", "nxp,p3h2840";
>
> This follows the fallback-compatible pattern used in other upstream bindings.
>
> Is this fine?
>
> properties:
>   compatible:
>     oneOf:
>       - const: nxp,p3h2840
>       - items:
>           - enum:
>               - nxp,p3h2440
>               - nxp,p3h2441
>               - nxp,p3h2841
>           - const: nxp,p3h2840
>
> Regards
> Lakshay

A gentle follow-up on my previous reply. Could you please confirm whether my understanding is correct before I prepare the next revision?

Regards,
Lakshay

  reply	other threads:[~2026-09-11  9:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  6:21 [PATCH v18 0/8] Add support for NXP P3H2x4x I3C hub driver Lakshay Piplani
2026-09-03  6:21 ` [PATCH v18 1/8] i3c: master: Add APIs for I3C hub support Lakshay Piplani
2026-09-03  6:34   ` sashiko-bot
2026-09-03  6:21 ` [PATCH v18 2/8] i3c: master: Add controller-only device operation helpers Lakshay Piplani
2026-09-03  6:35   ` sashiko-bot
2026-09-04 19:52   ` Frank Li
2026-09-03  6:21 ` [PATCH v18 3/8] dt-bindings: i3c: Add NXP P3H2x4x i3c-hub support Lakshay Piplani
2026-09-09  6:07   ` Krzysztof Kozlowski
2026-09-09  7:08     ` [EXT] " Lakshay Piplani
2026-09-09  7:14       ` Krzysztof Kozlowski
2026-09-09  8:32         ` Lakshay Piplani
2026-09-11  9:22           ` Lakshay Piplani [this message]
2026-09-03  6:21 ` [PATCH v18 4/8] mfd: p3h2x4x: Add driver for NXP P3H2x4x i3c hub and on-die regulator Lakshay Piplani
2026-09-03  6:35   ` sashiko-bot
2026-09-11  9:31   ` Lakshay Piplani
2026-09-03  6:21 ` [PATCH v18 5/8] regulator: p3h2x4x: Add driver for on-die regulators in NXP P3H2x4x i3c hub Lakshay Piplani
2026-09-03  6:31   ` sashiko-bot
2026-09-03  6:21 ` [PATCH v18 6/8] i3c: hub: Add support for the I3C interface in the I3C hub Lakshay Piplani
2026-09-03  6:38   ` sashiko-bot
2026-09-04 20:05   ` Frank Li
2026-09-03  6:21 ` [PATCH v18 7/8] i3c: hub: p3h2x4x: Add support for NXP P3H2x4x I3C hub functionality Lakshay Piplani
2026-09-04 20:10   ` Frank Li
2026-09-03  6:21 ` [PATCH v18 8/8] i3c: hub: p3h2x4x: Add SMBus slave mode support Lakshay Piplani
2026-09-03  6:41   ` sashiko-bot
2026-09-04 20:12   ` Frank Li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AS4PR04MB936261B25BA49E704DF2BD14FBBE2@AS4PR04MB9362.eurprd04.prod.outlook.com \
    --to=lakshay.piplani@nxp.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=aman.kumarpandey@nxp.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frank.li@nxp.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=priyanka.jain@nxp.com \
    --cc=robh@kernel.org \
    --cc=vikash.bansal@nxp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox