Re: [PATCH v5 0/5] i3c: Add basic HDR mode support

From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Frank Li" <Frank.Li@nxp.com>,
	"Miquel Raynal" <miquel.raynal@bootlin.com>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
	imx@lists.linux.dev, linux-iio@vger.kernel.org,
	joshua.yeong@starfivetech.com, devicetree@vger.kernel.org,
	"Carlos Song" <carlos.song@nxp.com>,
	"Adrian Fluturel" <fluturel.adrian@gmail.com>
Subject: Re: [PATCH v5 0/5] i3c: Add basic HDR mode support
Date: Mon, 13 Oct 2025 21:54:55 +0200	[thread overview]
Message-ID: <2025101319545551cfb399@mail.local> (raw)
In-Reply-To: <20251012180327.5d94dda2@jic23-huawei>

On 12/10/2025 18:03:27+0100, Jonathan Cameron wrote:
> On Tue, 07 Oct 2025 16:06:12 -0400
> Frank Li <Frank.Li@nxp.com> wrote:
> 
> > Add basic HDR mode support, only support private transfer, not support
> > CCC command.
> > 
> > Update i3c framework API to allow pass down mode and extend driver callback
> > function.
> > 
> > Implement HDR transfer in svc i3c master driver.
> > 
> > Simplifed HDR flow is (ref i3c spec line 5514) Figure 129
> > 
> > <--              SDR            ---> | <--- HDR
> > START 0x7E RnW(0) ACK CCC(ENTHDR0) T   HDR-CMD(00-7f write, 80--ff read)
> > 
> >                                     ----> |  
> > HDR-DATA HDR-CRC HDR-RESTART .... HDR-EXIT
> > 
> > Note: HDR-CMD is 16bit data, which included 7bit slave address and 8bit
> > read/write command.
> > 
> > svc hardware can auto issue SDR part.
> > 
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> 
> Whilst there will probably have to be a v6 for the ACPI ID issue in patch 5,
> I'd like to ask the question of how are we planning to merge this?
> 
> Maybe an immutable branch either in IIO or I3C trees that the other one picks up?
> 
> It's a new driver so could gamble on taking the IIO driver the I3C tree but even
> then I'd like a topic / immutable branch in case any IIO wide refactors or similar
> hit this cycle.
> 

I can definitively provide an immutable branch once this goes in or if
you are more comfortable with this, I guess there is no urgency and we
could apply this over two cycles, first the I3C part and then you can
take the driver.

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c