From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Navada Kanyana, Mukund" <navada@ti.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] regmap: Add support for continously numbered pages across regmap range
Date: Wed, 28 Nov 2012 11:34:43 +0000 [thread overview]
Message-ID: <20121128113443.GM32691@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <6817C817C9581447825BFB369EAC42163E959AED@DBDE01.ent.ti.com>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
On Wed, Nov 28, 2012 at 10:11:05AM +0000, Navada Kanyana, Mukund wrote:
Fix your mailer to word wrap within paragraphs.
> > I'm sorry but I can't understand what this is supposed to do. The
> > current paging code expects pages to be numbered continuously with no
> > gaps. Can you please clarify?
> But the page number is expected to increase only till end of range.
> But in devices like TLV320AIC3256, the page number increases beyond
> range.
What does this mean? How can we have a page beyond the end of the
range?
> Pages 0 through Page 1 --> first register range for device
> configuration. Page 8 through Page 16 --> second range for DSP1
> coefficient memory Page 26 through Page 34 --> third range for DSP2
> coefficient memory
> Window length of each page is 128. So if we need to correctly write
> the page number in selector register for second range, start_page_num
> would be 8. If we did not have start_page_num, it would write 0 to
> selector register.
I'm sorry but I don't understand how that would happen? What breaks
accessing page 8? This sounds like you're doing something wrong when
you're trying ton use the paging.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-28 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 9:22 [PATCH 1/1] regmap: Add support for continously numbered pages across regmap range Mukund Navada
2012-11-28 9:29 ` Mark Brown
2012-11-28 10:11 ` Navada Kanyana, Mukund
2012-11-28 11:34 ` Mark Brown [this message]
2012-11-28 11:52 ` Navada Kanyana, Mukund
2012-11-28 11:56 ` Mark Brown
2012-11-28 12:10 ` Navada Kanyana, Mukund
2012-11-28 13:15 ` 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=20121128113443.GM32691@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=navada@ti.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