From: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-kernel@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>, Graeme Gregory <gg@slimlogic.co.uk>,
Samuel Oritz <sameo@linux.intel.com>
Subject: Re: [PATCH 1/8] regmap: Introduce caching support
Date: Mon, 5 Sep 2011 11:00:15 +0100 [thread overview]
Message-ID: <20110905100015.GE30114@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4E649C81.3070203@metafoo.de>
On Mon, Sep 05, 2011 at 11:55:13AM +0200, Lars-Peter Clausen wrote:
> On 09/05/2011 11:43 AM, Dimitris Papastamos wrote:
> > [...]
> >>> /**
> >>> * Default value for a register. We use an array of structs rather
> >>> * than a simple array as many modern devices have very sparse
> >>> @@ -50,9 +55,11 @@ struct reg_default {
> >>> * (eg, a clear on read interrupt status register).
> >>> *
> >>> * @max_register: Optional, specifies the maximum valid register index.
> >>> - * @reg_defaults: Power on reset values for registers (for use with
> >>> - * register cache support).
> >>> - * @num_reg_defaults: Number of elements in reg_defaults.
> >>> + *
> >>> + * @cache_type: The actual cache type.
> >>> + * @cache_defaults_raw: Power on reset values for registers (for use with
> >>> + * register cache support).
> >>> + * @num_cache_defaults_raw: Number of elements in cache_defaults_raw.
> >>> */
> >>> struct regmap_config {
> >>> int reg_bits;
> >>> @@ -64,8 +71,10 @@ struct regmap_config {
> >>> bool (*precious_reg)(struct device *dev, unsigned int reg);
> >>>
> >>> unsigned int max_register;
> >>> - struct reg_default *reg_defaults;
> >>> - int num_reg_defaults;
> >>
> >> I guess these were removed by accident due to some merge conflict as they were
> >> added just recently. It would be good if you could re-add them and if they are
> >> set initialize cache_defaults using a memdup instead of reading cache_defaults_raw.
> >>
> >>> +
> >>> + enum regcache_type cache_type;
> >>> + const void *cache_defaults_raw;
> >>> + unsigned num_cache_defaults_raw;
> >>> };
> >>>
> >>> typedef int (*regmap_hw_write)(struct device *dev, const void *data,
> >
> > I was merely renaming these.
>
> And you changed the type. We need the reg_default type register defaults for
> devices which have a sparse registers set or where the base register address is
> at a larger offset.
>
> - Lars
Aw duh, yes. Will add support to regcache to be able to use directly
the reg_defaults if they have been provided by the user without having
to derive this from cache_defaults_raw.
Thanks,
Dimitris
next prev parent reply other threads:[~2011-09-05 10:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 15:46 [PATCH 0/8] Introduce caching support for regmap Dimitris Papastamos
2011-09-02 15:46 ` [PATCH 1/8] regmap: Introduce caching support Dimitris Papastamos
2011-09-02 20:02 ` Lars-Peter Clausen
2011-09-02 23:48 ` Mark Brown
2011-09-03 1:10 ` Dimitris Papastamos
2011-09-04 15:57 ` Mark Brown
2011-09-05 9:44 ` Dimitris Papastamos
2011-09-05 9:43 ` Dimitris Papastamos
2011-09-05 9:55 ` Lars-Peter Clausen
2011-09-05 10:00 ` Dimitris Papastamos [this message]
2011-09-02 15:46 ` [PATCH 2/8] regmap: Add the indexed cache support Dimitris Papastamos
2011-09-02 20:16 ` Lars-Peter Clausen
2011-09-05 9:55 ` Dimitris Papastamos
2011-09-05 10:14 ` Lars-Peter Clausen
2011-09-05 18:22 ` Mark Brown
2012-07-17 11:16 ` Mark Brown
2012-07-17 14:24 ` Lars-Peter Clausen
2011-09-02 15:46 ` [PATCH 3/8] regmap: Add the rbtree " Dimitris Papastamos
2011-09-02 20:22 ` Lars-Peter Clausen
2011-09-05 9:58 ` Dimitris Papastamos
2011-09-02 15:46 ` [PATCH 4/8] regmap: Add the LZO " Dimitris Papastamos
2011-09-05 21:40 ` Matthieu CASTET
2011-09-07 19:19 ` Mark Brown
2011-09-02 15:46 ` [PATCH 5/8] regmap: Add the regcache_sync trace event Dimitris Papastamos
2011-09-02 15:46 ` [PATCH 6/8] regmap: Incorporate the regcache core into regmap Dimitris Papastamos
2011-09-02 15:46 ` [PATCH 7/8] regmap: It is impossible to be given a NULL defaults cache Dimitris Papastamos
2011-09-02 15:46 ` [PATCH 8/8] regmap: Support NULL cache_defaults_raw 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=20110905100015.GE30114@opensource.wolfsonmicro.com \
--to=dp@opensource.wolfsonmicro.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=sameo@linux.intel.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