linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xiubo Li <lixiubo@cmss.chinamobile.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regmap: flat: introduce register striding to savesomememories
Date: Thu, 31 Dec 2015 09:36:41 +0800	[thread overview]
Message-ID: <568486A9.10602@cmss.chinamobile.com> (raw)
In-Reply-To: <20151230175830.GA16023@sirena.org.uk>



On 31/12/2015 01:58, Mark Brown wrote:
> On Fri, Dec 18, 2015 at 04:59:38PM +0800, lixiubo@cmss.chinamobile.com wrote:
>
>>> I think we'll need to continue supporting non power of two strides so
>>> an unconditional conversion to shifts might be an issue - some weird DSP
>>> probably does that.
>
>> Yes, agreed.
>
>> IMO this won't happen to MMIO, and for the device using MMIO the
>> register strides should equal to power of two.
>
>> Are there some cases I have met?
>
> DSPs exposed via I2C and SPI are the main things I'm worried about.
> It's fairly common for DSPs to have unusual word sizes including things
> like three bytes.
>

Yes, if so, for this case the non power of two strides should be still 
supported.

Thanks for your promotion, and I will think over of this carefully.

BRs

Xiubo Li





      reply	other threads:[~2015-12-31  1:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14  7:14 [PATCH] regmap: flat: introduce register striding to save some memories Xiubo Li
2015-12-14 17:57 ` Mark Brown
     [not found]   ` <566FD138.4010601@cmss.chinamobile.com>
2015-12-18  8:23     ` [PATCH] regmap: flat: introduce register striding to save somememories Mark Brown
     [not found]       ` <2015121816593812599420@cmss.chinamobile.com>
2015-12-30 17:58         ` Mark Brown
2015-12-31  1:36           ` Xiubo Li [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=568486A9.10602@cmss.chinamobile.com \
    --to=lixiubo@cmss.chinamobile.com \
    --cc=broonie@kernel.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;
as well as URLs for NNTP newsgroup(s).