From: Srinivas KANDAGATLA <srinivas.kandagatla@st.com>
To: Mark Brown <broonie@kernel.org>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] regmap: debugfs: Fix start_reg calculation (v2)
Date: Mon, 13 May 2013 07:53:33 +0100 [thread overview]
Message-ID: <51908DED.7090701@st.com> (raw)
In-Reply-To: <20130512145906.GC4046@sirena.org.uk>
Hi Mark,
On 12/05/13 15:59, Mark Brown wrote:
> On Wed, May 08, 2013 at 11:20:09AM +0100, Srinivas KANDAGATLA wrote:
>> From: Srinivas Kandagatla <srinivas.kandagatla@st.com>
>>
>> If we dump syscon regmap registers via debugfs you will notice that the
>> dump contains lot of XXXXXXXX values.
>
> Sorry, can you please rebase this against v3.10-rc1? This patch was
> against v3.9 and I'm not now convinced that the issue still exists.
>
I did try 3.10-rc1, and I can not reproduce the issue.
very similar patch "regmap: debugfs: Simplify calculation of
`c->max_reg'" addressed the issue.
However It looks like one of the return from the
regmap_debugfs_get_dump_start() still returns wrong register offset.
<snip>
if (from >= c->min && from <= c->max) {
fpos_offset = from - c->min;
reg_offset = fpos_offset / map->debugfs_tot_len;
*pos = c->min + (reg_offset * map->debugfs_tot_len);
mutex_unlock(&map->cache_lock);
return c->base_reg + reg_offset;
}
</snip>
Thanks,
srini
next prev parent reply other threads:[~2013-05-13 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 10:20 [PATCH v2] regmap: debugfs: Fix start_reg calculation (v2) Srinivas KANDAGATLA
2013-05-08 12:40 ` Mark Brown
2013-05-12 14:59 ` Mark Brown
2013-05-13 6:53 ` Srinivas KANDAGATLA [this message]
2013-05-13 14: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=51908DED.7090701@st.com \
--to=srinivas.kandagatla@st.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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