Received-SPF: pass (google.com: domain of linux-kernel+bounces-198151-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
From: Andy Shevchenko <andy.shevchenko@gmail.com>
Date: Sun, 2 Jun 2024 10:29:07 +0300
To: Jim Wylder <jwylder@google.com>
Cc: Mark Brown <broonie@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>, kernel-team@android.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] regmap-i2c: Subtract reg size from max_write
Message-ID: <ZlwfQ3ERbo5snLcK@surfacebook.localdomain>
References: <20240523211437.2839942-1-jwylder@google.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20240523211437.2839942-1-jwylder@google.com>

Thu, May 23, 2024 at 04:14:36PM -0500, Jim Wylder kirjoitti:
> Currently, when an adapter defines a max_write_len quirk,
> the data will be chunked into data sizes equal to the
> max_write_len quirk value.  But the payload will be increased by
> the size of the register address before transmission.  The
> resulting value always ends up larger than the limit set
> by the quirk.
> 
> Avoid this error by setting regmap's max_write to the quirk's
> max_write_len minus the number of bytes for the register and
> padding.  This allows the chunking to work correctly for this
> limited case without impacting other use-cases.

...

>  		    (bus->max_raw_write == 0 || bus->max_raw_write > quirks->max_write_len))
> -			max_write = quirks->max_write_len;
> +			max_write = quirks->max_write_len -
> +				(config->reg_bits + config->pad_bits) / BITS_PER_BYTE;

Interesting. regmap-spi does this slightly differently, i.e. reg/8 + pad/8.
I'm wondering which one is more correct (potential off-by-one I suppose).

-- 
With Best Regards,
Andy Shevchenko