From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Mark Brown <broonie@kernel.org>,
Cristian Birsan <cristian.birsan@microchip.com>
Cc: <ludovic.desroches@atmel.com>,
<alexandre.belloni@free-electrons.com>,
<boris.brezillon@free-electrons.com>, <ce3a@gmx.de>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] regmap: debugfs: Add support for dumping write only device registers
Date: Fri, 5 Aug 2016 10:26:34 +0200 [thread overview]
Message-ID: <3e42070f-a480-dbf4-1a97-b7172bebb1cc@atmel.com> (raw)
In-Reply-To: <20160804202646.GH10383@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1775 bytes --]
Le 04/08/2016 à 22:26, Mark Brown a écrit :
> On Thu, Aug 04, 2016 at 05:55:58PM +0300, Cristian Birsan wrote:
>> Add support for dumping write only device registers in debugfs. This is
>> useful for audio codecs that have write only registers (like WM8731).
>> The logic that decides if a value can be printed is moved to
>> regmap_printable() function to allow for easier future updates.
>
> Please check your CC list when sending things upstream - try to ensure
> that people you're sending patches to are relevant to the patch.
> Maintainers often get lots of mail and having to sort out mail that's
> not really relevant to them can make it easier for relevant mail to get
> missed.
Mark,
Just FYI, I gave Cristian the CC list he could use: In fact the Atmel /
Microchip / Free-Electons people are in the list because we are all
working together on the AT91 platforms now. And these platforms use the
audio codec Cristian is working on.
>> +static bool regmap_printable(struct regmap *map, unsigned int reg)
>> +{
>> + if (regmap_precious(map, reg))
>> + return false;
>> +
>> + if (!regmap_readable(map, reg) && !regmap_cached(map, reg))
>> + return false;
>> +
>> + return true;
>> +}
>
> This only has one user...
>
>> for (i = start_reg; i <= to; i += map->reg_stride) {
>> - if (!regmap_readable(map, i))
>> + if (!regmap_readable(map, i) && !regmap_cached(map, i))
>> continue;
>>
>
> ...though it could have more.
>
>> - ret = regmap_read(map, i, &val);
>> + if (regmap_readable(map, i))
>> + ret = regmap_read(map, i, &val);
>> + else
>> + ret = regcache_read(map, i, &val);
>> +
>
> I don't understand this change, a read will go to cache anyway.
>
--
Nicolas Ferre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-08-05 8:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 14:55 [PATCH 0/2] Display regmap values in debugfs for write only registers Cristian Birsan
2016-08-04 14:55 ` [PATCH 1/2] regmap: Add a function to check if a regmap register is cached Cristian Birsan
2016-08-04 15:39 ` Lars-Peter Clausen
2016-08-04 15:48 ` Mark Brown
2016-08-08 15:44 ` [PATCH v2 0/2] Display regmap values in debugfs for write only registers Cristian Birsan
2016-08-08 15:44 ` [PATCH v2 1/2] regmap: Add a function to check if a regmap register is cached Cristian Birsan
2016-08-09 12:44 ` Applied "regmap: Add a function to check if a regmap register is cached" to the regmap tree Mark Brown
2016-08-08 15:44 ` [PATCH v2 2/2] regmap: debugfs: Add support for dumping write only device registers Cristian Birsan
2016-08-09 12:44 ` Applied "regmap: debugfs: Add support for dumping write only device registers" to the regmap tree Mark Brown
2016-08-09 13:11 ` kbuild test robot
2016-08-09 13:18 ` kbuild test robot
2016-08-10 12:15 ` Cristian Birsan
2016-08-04 14:55 ` [PATCH 2/2] regmap: debugfs: Add support for dumping write only device registers Cristian Birsan
2016-08-04 20:26 ` Mark Brown
2016-08-05 8:26 ` Nicolas Ferre [this message]
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=3e42070f-a480-dbf4-1a97-b7172bebb1cc@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=broonie@kernel.org \
--cc=ce3a@gmx.de \
--cc=cristian.birsan@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.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
all inboxes | Powered by JetHome®