[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7e556c50-a98c-a715-9b80-209dd79cdc29@intel.com>
Date: Fri, 16 Jun 2023 15:51:55 -0700
From: Russ Weight <russell.h.weight@...el.com>
To: Mark Brown <broonie@...nel.org>
CC: Jim Wylder <jwylder@...gle.com>,
"Gerlach, Matthew" <matthew.gerlach@...ux.intel.com>,
<linux-kernel@...r.kernel.org>,
"Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [BUG] _regmap_raw_write() - divide-by-zero
On 6/16/23 15:14, Mark Brown wrote:
> On Fri, Jun 16, 2023 at 02:58:24PM -0700, Russ Weight wrote:
>
>> The origination of the regmap->max_raw_write value is here:
>> https://github.com/torvalds/linux/blob/4973ca29552864a7a047ab8a15611a585827412f/drivers/base/regmap/regmap-spi-avmm.c#L663
>>> .max_raw_write = SPI_AVMM_VAL_SIZE * MAX_WRITE_CNT,
>> SPI_AVMM_VAL_SIZE is defined as 4, and MAX_WRITE_CNT is defined as 1
> This should add in some headroom for the value too.
Thanks for the guidance, Mark. We'll put a patch together to fix up the config.
- Russ
>
> We should also fix the max_raw_write comments since it's a bit confusing
> between users and buses, though AFAICT nothing outside the core ever
> checks.
Powered by blists - more mailing lists