From: Krzysztof Kozlowski <krzk@kernel.org>
To: Lakshay Piplani <lakshay.piplani@nxp.com>,
"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: Wed, 9 Sep 2026 09:14:56 +0200 [thread overview]
Message-ID: <624665dc-8f5a-4818-8786-c1c2356e58e4@kernel.org> (raw)
In-Reply-To: <AS4PR04MB9362BEAE2ADA8087F00DADFEFBB02@AS4PR04MB9362.eurprd04.prod.outlook.com>
On 09/09/2026 09:08, Lakshay Piplani wrote:
>>> +description: |
>>> + P3H2x4x (P3H2440/P3H2441/P3H2840/P3H2841) is a family of multiport
>>> +I3C
>>> + hub devices that connect to:-
>>> + 1. A host CPU via I3C/I2C/SMBus bus on upstream side and connect to
>> multiple
>>> + peripheral devices on the downstream side.
>>> + 2. Have two Controller Ports which can support either
>>> + I2C/SMBus or I3C buses and connect to a CPU, BMC or SOC.
>>> + 3. P3H2840/ P3H2841 are 8 port I3C hub with eight Target Ports.
>>> + 4. P3H2440/ P3H2441 are 4 port I3C hub with four Target Ports.
>>> + Target ports can be configured as SMBus or I3C and connect to
>>> + peripherals.
>>> +
>>> + All variants use the same register interface. Software reads the
>>> + number of target ports from DEV_CAPAB. The x0/x1 variants differ in
>>> + their power-up defaults, which the driver replaces with the DT
>> configuration.
>>
>> I don't understand what this driver reference means and what is its purpose
>> here.
>
> Okay, I will update the description accordingly to only convey the hardware details.
>
>>
>>> +
>>> +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.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-09 7:15 UTC|newest]
Thread overview: 20+ 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:21 ` [PATCH v18 2/8] i3c: master: Add controller-only device operation helpers Lakshay Piplani
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 [this message]
2026-09-09 8:32 ` Lakshay Piplani
2026-09-11 9:22 ` Lakshay Piplani
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-11 9:31 ` Lakshay Piplani
2026-09-15 11:14 ` Lee Jones
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:21 ` [PATCH v18 6/8] i3c: hub: Add support for the I3C interface in the I3C hub Lakshay Piplani
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-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=624665dc-8f5a-4818-8786-c1c2356e58e4@kernel.org \
--to=krzk@kernel.org \
--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=lakshay.piplani@nxp.com \
--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
all inboxes | Powered by JetHome®