The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Lakshay Piplani <lakshay.piplani@nxp.com>
Cc: "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>,
	Frank Li <frank.li@nxp.com>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	Vikash Bansal <vikash.bansal@nxp.com>,
	Priyanka Jain <priyanka.jain@nxp.com>,
	Aman Kumar Pandey <aman.kumarpandey@nxp.com>
Subject: Re: [EXT] Re: [PATCH v13 3/7] mfd: p3h2x4x: Add driver for NXP P3H2x4x i3c hub and on-die regulator
Date: Thu, 9 Jul 2026 11:11:25 +0100	[thread overview]
Message-ID: <20260709101125.GE2045740@google.com> (raw)
In-Reply-To: <PAXPR04MB935077516683DD73CADC0FC6FBFE2@PAXPR04MB9350.eurprd04.prod.outlook.com>

On Thu, 09 Jul 2026, Lakshay Piplani wrote:

> > > --- /dev/null
> > > +++ b/drivers/mfd/p3h2840.c
> > > @@ -0,0 +1,126 @@
> > > +// SPDX-License-Identifier: GPL-2.0
> > > +/*
> > > + * Copyright 2025-2026 NXP
> > 
> > Nit: '\n' here.
> > 
> 
> Sure, will remove the extra blank line.

In future, you only need to reply to review comments that you don't
agree with or require more information.  Snip the rest please.

> > > +static const struct regmap_config p3h2x4x_regmap_config = {
> > > +     .reg_bits = P3H2X4X_REG_BITS,
> > > +     .val_bits = P3H2X4X_VAL_BITS,
> > > +     .max_register = 0xFF,
> > > +};
> > > +
> > > +static int p3h2x4x_device_probe_i3c(struct i3c_device *i3cdev)
> > 
> > How many of these are comming down the pipe?
> > 
> > Might be worth expanding drivers/mfd/simple-mfd-i2c.c instead?
> 
> The P3H2x4x MFD supports both I2C and I3C transports. While the I2C path is conceptually similar to simple-mfd-i2c.c,
> the I3C path additionally requires device matching/probing, devm_regmap_init_i3c(), PID/manufacturer validation, and 
> retaining the parent struct i3c_device * for use by the hub child driver. As these requirements are specific to I3C 
> and not handled by the existing simple-MFD helpers, I believe a dedicated MFD driver is the more suitable approach.

Sure.  What I'm saying is; taking into consideration that this device
doesn't do anything useful (beyond generic device registration that
'simple' provides), if there are lots of I3C based devices coming, it
may be more prudent to create an I3C version.

However, it's probably too early to make that call.

> > >  enum i3c_dcr {
> > >       I3C_DCR_GENERIC_DEVICE = 0,
> > > +     I3C_DCR_HUB = 194,
> > 
> > What is this value?
> 
> 194 is the Device Characteristics Register (DCR) value assigned to I3C Hub devices by the MIPI I3C specification.

Is it described in base-10?  Registers are usually described in hex.

-- 
Lee Jones

  reply	other threads:[~2026-07-09 10:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01  6:57 [PATCH v13 0/7] Add support for NXP P3H2x4x I3C hub driver Lakshay Piplani
2026-07-01  6:57 ` [PATCH v13 1/7] i3c: master: Add APIs for I3C hub support Lakshay Piplani
2026-07-01  6:57 ` [PATCH v13 2/7] dt-bindings: i3c: Add NXP P3H2x4x i3c-hub support Lakshay Piplani
2026-07-01  6:57 ` [PATCH v13 3/7] mfd: p3h2x4x: Add driver for NXP P3H2x4x i3c hub and on-die regulator Lakshay Piplani
2026-07-08 19:20   ` Lee Jones
2026-07-09  4:49     ` [EXT] " Lakshay Piplani
2026-07-09 10:11       ` Lee Jones [this message]
2026-07-01  6:57 ` [PATCH v13 4/7] regulator: p3h2x4x: Add driver for on-die regulators in NXP P3H2x4x i3c hub Lakshay Piplani
2026-07-01  6:57 ` [PATCH v13 5/7] i3c: hub: Add support for the I3C interface in the I3C hub Lakshay Piplani
2026-07-01  6:57 ` [PATCH v13 6/7] i3c: hub: p3h2x4x: Add support for NXP P3H2x4x I3C hub functionality Lakshay Piplani
2026-07-01  6:57 ` [PATCH v13 7/7] i3c: hub: p3h2x4x: Add SMBus slave mode support Lakshay Piplani

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=20260709101125.GE2045740@google.com \
    --to=lee@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=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