The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Charles Keepax <ckeepax@opensource.cirrus.com>,
	Richard Fitzgerald <rf@opensource.cirrus.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regcache: Use a consistent sort for defaults table
Date: Thu, 6 Aug 2026 11:23:37 +0300	[thread overview]
Message-ID: <38c16850-57de-4d6d-bdef-ef1270d5bd19@linux.intel.com> (raw)
In-Reply-To: <20260805-regmap-regcache-sort-v1-1-162186aad8b9@kernel.org>



On 05/08/2026 20:51, Mark Brown wrote:
> When we look up registers in the defaults table we use a binary search,
> and we have a regcache_sort_defaults() API to help drivers that constuct
> their defaults tables on the fly.  Unfortunately the lookup and the sort
> don't use the same comparison function, and to make matters worse the
> comparison function used during lookups is written for signed register
> numbers rather than the unsigned ones we actually have so can produce
> suprising results when some of the addresses have the top bit set.
> 
> Standardise on the more explicitly coded function to ensure consistent
> results.

Reviewed-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>

> 
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
>  drivers/base/regmap/regcache.c | 10 +---------
>  1 file changed, 1 insertion(+), 9 deletions(-)
> 
> diff --git a/drivers/base/regmap/regcache.c b/drivers/base/regmap/regcache.c
> index aa8f2efed779..480bc76f9a02 100644
> --- a/drivers/base/regmap/regcache.c
> +++ b/drivers/base/regmap/regcache.c
> @@ -727,14 +727,6 @@ unsigned int regcache_get_val(struct regmap *map, const void *base,
>  	return -1;
>  }
>  
> -static int regcache_default_cmp(const void *a, const void *b)
> -{
> -	const struct reg_default *_a = a;
> -	const struct reg_default *_b = b;
> -
> -	return _a->reg - _b->reg;
> -}
> -
>  int regcache_lookup_reg(struct regmap *map, unsigned int reg)
>  {
>  	struct reg_default key;
> @@ -744,7 +736,7 @@ int regcache_lookup_reg(struct regmap *map, unsigned int reg)
>  	key.def = 0;
>  
>  	r = bsearch(&key, map->reg_defaults, map->num_reg_defaults,
> -		    sizeof(struct reg_default), regcache_default_cmp);
> +		    sizeof(struct reg_default), regcache_defaults_cmp);
>  
>  	if (r)
>  		return r - map->reg_defaults;
> 
> ---
> base-commit: 075b74841bd0065a3bda3440873c747938e69b68
> change-id: 20260805-regmap-regcache-sort-8d144a68bf8d
> 
> Best regards,
> --  
> Mark Brown <broonie@kernel.org>
> 

-- 
Péter


  reply	other threads:[~2026-08-06  8:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 17:51 [PATCH] regcache: Use a consistent sort for defaults table Mark Brown
2026-08-06  8:23 ` Péter Ujfalusi [this message]
2026-08-06  8:46 ` Charles Keepax
2026-08-06 12:00 ` Mark Brown

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=38c16850-57de-4d6d-bdef-ef1270d5bd19@linux.intel.com \
    --to=peter.ujfalusi@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=rf@opensource.cirrus.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