From: Krzysztof Kozlowski <krzk@kernel.org>
To: Aman Kumar Pandey <aman.kumarpandey@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>
Cc: Vikash Bansal <vikash.bansal@nxp.com>,
Priyanka Jain <priyanka.jain@nxp.com>,
Shashank Rebbapragada <shashank.rebbapragada@nxp.com>,
Frank Li <frank.li@nxp.com>
Subject: Re: [EXT] Re: [PATCH v2 1/2] dt-bindings: i3c: Add NXP P3H2x4x i3c-hub support
Date: Wed, 14 May 2025 12:18:46 +0200 [thread overview]
Message-ID: <18d6951a-860e-4479-837e-9edc90adeaea@kernel.org> (raw)
In-Reply-To: <GVXPR04MB9778335A5DFAB37CC8D011FC9997A@GVXPR04MB9778.eurprd04.prod.outlook.com>
On 12/05/2025 13:45, Aman Kumar Pandey wrote:
>>
>
> These are not vender specific properties. all these properties are as per i3c hub specification.
> What should I change for above properties ?
BTW, if this was I3C spec, then I would also expect all of such
spec-related-properties to be in shared schema.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-14 10:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 4:57 [PATCH v2 1/2] dt-bindings: i3c: Add NXP P3H2x4x i3c-hub support Aman Kumar Pandey
2025-05-08 4:57 ` [PATCH v2 2/2] drivers: i3c: Add driver for NXP P3H2x4x i3c-hub device Aman Kumar Pandey
2025-05-08 6:09 ` Krzysztof Kozlowski
2025-05-12 11:45 ` [EXT] " Aman Kumar Pandey
2025-05-14 10:05 ` Krzysztof Kozlowski
2025-05-09 12:28 ` kernel test robot
2025-05-08 6:07 ` [PATCH v2 1/2] dt-bindings: i3c: Add NXP P3H2x4x i3c-hub support Krzysztof Kozlowski
2025-05-12 11:45 ` [EXT] " Aman Kumar Pandey
2025-05-14 10:10 ` Krzysztof Kozlowski
2025-05-22 18:46 ` Frank Li
2025-05-14 10:18 ` Krzysztof Kozlowski [this message]
2025-05-22 18:38 ` Frank Li
2025-05-08 6:09 ` Rob Herring (Arm)
2025-05-09 8:10 ` kernel test robot
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=18d6951a-860e-4479-837e-9edc90adeaea@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=aman.kumarpandey@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frank.li@nxp.com \
--cc=krzk+dt@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=priyanka.jain@nxp.com \
--cc=robh@kernel.org \
--cc=shashank.rebbapragada@nxp.com \
--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;
as well as URLs for NNTP newsgroup(s).