All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nariman Poushin <nariman@opensource.wolfsonmicro.com>
To: broonie@kernel.org
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: [RFC][PATCH] regmap: make REGCACHE_NONE maps return error on regcache_sync
Date: Fri, 8 May 2015 10:55:37 +0100	[thread overview]
Message-ID: <20150508095537.GA15394@opensource.wolfsonmicro.com> (raw)

Signed-off-by: Nariman Poushin <nariman@opensource.wolfsonmicro.com>
---
 regcache currently causes a BUG_ON if cache_sync/sync_region is
 called on a map with cache_type REGCACHE_NONE. This is not
 consistent with the behaviour of regcache_read/write which
 currently just return -ENOSYS and only throws a BUG_ON if
 the cache_type is something that _should_ have cache ops,
 but doesn't. Sure your device might not work, it but doesn't
 seem right to panic the kernel. The other option I suppose
 is to change it to a WARN_ON.

 Thanks
 Nariman

 drivers/base/regmap/regcache.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/base/regmap/regcache.c b/drivers/base/regmap/regcache.c
index 7eb7b3b..992aba3 100644
--- a/drivers/base/regmap/regcache.c
+++ b/drivers/base/regmap/regcache.c
@@ -303,6 +303,9 @@ int regcache_sync(struct regmap *map)
 	const char *name;
 	unsigned int bypass;
 
+	if (map->cache_type == REGCACHE_NONE)
+		return -ENODEV;
+
 	BUG_ON(!map->cache_ops);
 
 	map->lock(map->lock_arg);
@@ -371,6 +374,9 @@ int regcache_sync_region(struct regmap *map, unsigned int min,
 	const char *name;
 	unsigned int bypass;
 
+	if (map->cache_type == REGCACHE_NONE)
+		return -ENODEV;
+
 	BUG_ON(!map->cache_ops);
 
 	map->lock(map->lock_arg);
-- 
2.1.4


             reply	other threads:[~2015-05-08  9:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08  9:55 Nariman Poushin [this message]
2015-05-08 10:20 ` [RFC][PATCH] regmap: make REGCACHE_NONE maps return error on regcache_sync Mark Brown
2015-05-08 10:34   ` Nariman Poushin
2015-06-08 14:16     ` Nariman Poushin
2015-06-08 17:24       ` 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=20150508095537.GA15394@opensource.wolfsonmicro.com \
    --to=nariman@opensource.wolfsonmicro.com \
    --cc=broonie@kernel.org \
    --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.