From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: linux-kernel@vger.kernel.org, Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH 1/2] regmap: allow busses to request formatting with specific endianness
Date: Thu, 24 May 2012 00:16:42 +0100 [thread overview]
Message-ID: <20120523231641.GA5361@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1337812434-7609-1-git-send-email-swarren@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
On Wed, May 23, 2012 at 04:33:53PM -0600, Stephen Warren wrote:
> I'm not 100% sure if this is the approach you had in mind. However, anything
> more all-encompassing would require separating the concepts of endianness and
I wouldn't do this on the bus in the first instance, I'd do it on the
device - it's pretty much orthogonal to the bus what the device wants
and it's perfectly plausible that a device on another bus might've made
unusual endiannness choices. Otherwise it's pretty much what I was
thinking of.
For MMIO I'd expect that a large proportion of devices on platform buses
would pick native endianness.
> serialization that are coupled together in functions like
> regmap_format_4_12_write, and I'm not sure how that would work conceptually.
Anything using format_write() can be ignored, it's already lost large
chunks of functionality just from that. Non-integer byte sizes cause
issues.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-23 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 22:33 [PATCH 1/2] regmap: allow busses to request formatting with specific endianness Stephen Warren
2012-05-23 22:33 ` [PATCH 2/2] regmap: mmio: request native endian formatting Stephen Warren
2012-05-23 23:16 ` Mark Brown [this message]
2012-05-23 23:28 ` [PATCH 1/2] regmap: allow busses to request formatting with specific endianness Stephen Warren
2012-05-23 23:35 ` 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=20120523231641.GA5361@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.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