From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 13A7D375F7B; Thu, 9 Jul 2026 10:11:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783591892; cv=none; b=oTWbMjXEshQHoGHte6onGI4e/mkO6ZCe8Lng0R5ekOLyIyz0I0obVI7m6Le8FrMCdrmEcHdZHSIia4OU5cVHIoGlGO4LdMewP2PF2GvJy+jw68HGrKWsl1K4FFB8mgg2m63Q95Xt8HXInHXC+Vx/rUFB/SfbhIvsu7NdCbTec7o= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783591892; c=relaxed/simple; bh=pRhxwqWOfP7ccaJZFua4lYcw97ERlbtyggpPE/mOZLw=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=TWDkMMOwRh4bmxDeizp0/PivsrwDeGQP5JZR97EwqkFAMm1g41FcvGfptXuB534pP8/s5BRjLRl0bUcY0OyIQf9PX+y2JSYERbuTQcbn1keYeawVQRFcyOIKTtrpyLqV07csTrAj4kW3NHJiJTEKKu8onAsFJbZkt6JcPlJ8Qq0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Ge9pmZYC; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Ge9pmZYC" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 041B71F00A3A; Thu, 9 Jul 2026 10:11:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1783591890; bh=B2OZqhPNbHPz2NNiIEyBu8B9EXpp87800ccaAr1cLSA=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=Ge9pmZYCCrMDIafhqKOcMhWdfl0kOvTMKId4wiFTsyTZSrwq9g9guaBtzXnuHnz/G mCEIGpIfD5Nk6gpDjeCFFBRiFyxn6Kk15wkUECf7SgKVhaqk9oHaqpoP++yt5zkpcA Z6qgZ4iwSfp1Ra36lEkRn2aRGsmusnj4s+aP6Vmx+gp8GjQ9kP3zZjT4wpTNgq6iJd I0JZ8ZWn/yiPxfpAnJedRVQ+twXQ0o8BIxcr+D36tD/k32CC7B9gPFfxnIH3VAN1uw EvvF/2tZCcXh5MBwGbf7loNoB9dfaeUXB6o6Qu/E03m1RWFNqXFMJg91FxCN/yu+0J 1yTs5l56Z2CfA== Date: Thu, 9 Jul 2026 11:11:25 +0100 From: Lee Jones To: Lakshay Piplani Cc: "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" , Frank Li , "lgirdwood@gmail.com" , Vikash Bansal , Priyanka Jain , Aman Kumar Pandey Subject: Re: [EXT] Re: [PATCH v13 3/7] mfd: p3h2x4x: Add driver for NXP P3H2x4x i3c hub and on-die regulator Message-ID: <20260709101125.GE2045740@google.com> References: <20260701065755.2067793-1-lakshay.piplani@nxp.com> <20260701065755.2067793-4-lakshay.piplani@nxp.com> <20260708192034.GA1727174@google.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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