All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 2/2] regmap: Allow caches for devices with no defaults
Date: Mon, 10 Oct 2011 09:41:26 +0100	[thread overview]
Message-ID: <20111010084126.GA2563@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1318167876-17801-2-git-send-email-broonie@opensource.wolfsonmicro.com>

On Sun, Oct 09, 2011 at 02:44:36PM +0100, Mark Brown wrote:
> We only really need the defaults in order to cut down the number of
> registers we sync and to satisfy reads while the device is powered off
> but not all devices are going to need to do that (always on devices like
> PMICs being the prime example) so don't require those devices to supply
> a default.  Instead only try to fall back to hardware defaults if the
> driver told us to.
> 
> Devices using LZO won't be able to instantiate with this, that will require
> some updates in the LZO code to handle this case.
> 
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
>  drivers/base/regmap/regcache.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/base/regmap/regcache.c b/drivers/base/regmap/regcache.c
> index 67c7703..666f6f5 100644
> --- a/drivers/base/regmap/regcache.c
> +++ b/drivers/base/regmap/regcache.c
> @@ -120,7 +120,7 @@ int regcache_init(struct regmap *map)
>  		if (!tmp_buf)
>  			return -ENOMEM;
>  		map->reg_defaults = tmp_buf;
> -	} else {
> +	} else if (map->num_reg_defaults_raw) {
>  		/* Some devices such as PMICs don't have cache defaults,
>  		 * we cope with this by reading back the HW registers and
>  		 * crafting the cache defaults by hand.
> -- 
> 1.7.6.3

We could probably then also remove the first check in
regcache_hw_init() I guess.

The one:

if (!map->num_reg_defaults_raw)
	return -EINVAL;

Thanks,
Dimitris

  parent reply	other threads:[~2011-10-10  8:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09 13:44 [PATCH 1/2] regmap: Return a sensible error code if we fail to read the cache Mark Brown
2011-10-09 13:44 ` [PATCH 2/2] regmap: Allow caches for devices with no defaults Mark Brown
2011-10-09 17:43   ` Valdis.Kletnieks
2011-10-09 19:34     ` Mark Brown
2011-10-10  8:41   ` Dimitris Papastamos [this message]
2011-10-10  9:23     ` Mark Brown
2011-10-10 10:50       ` Dimitris Papastamos
2011-10-10  9:03 ` [PATCH 1/2] regmap: Return a sensible error code if we fail to read the cache Dimitris Papastamos

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=20111010084126.GA2563@opensource.wolfsonmicro.com \
    --to=dp@opensource.wolfsonmicro.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.