From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Robert Rosengren <robert.rosengren@axis.com>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jean Delvare <jdelvare@suse.de>
Subject: Re: [PATCH] regmap: Fix i2c word access when using SMBus access functions
Date: Tue, 3 Feb 2015 11:42:10 +0000 [thread overview]
Message-ID: <20150203114210.GG21293@sirena.org.uk> (raw)
In-Reply-To: <54CF89EA.9040206@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
On Mon, Feb 02, 2015 at 06:30:02AM -0800, Guenter Roeck wrote:
> On 02/02/2015 03:56 AM, Mark Brown wrote:
> >Yes, we really ought to handle _NATIVE too (though the chances of it
> >being used with I2C are minimal, it's mostly for MMIO). This also feels
> Well, we do; it is handled similar to the big endian case with the current
> code. Do you think it should be handled differently ? If yes, how ?
Perhaps it just needs to be more explicit about how it's handling native
endian? I didn't spot it.
> >like it's something that should be being handled further up the stack in
> >the serialization code but given that there's direct functions for this
> >in the smbus code perhaps it's better here. Or perhaps the smbus
> >support ought to be transitioned to use the bus interface and set
> >reg_write() and reg_read() operations now that we can do that, it seems
> >like a better fit though it might break compatibility with wierd devices.
> I thought about that, but since the smbus functions perform endianness
> conversion it would mean that I would have to undo that conversion just
> to have it done again.
No, the whole point is that by doing this you avoid any endianness
conversions or formatting in the framework at all so you can just use
the smbus functions to handle the formatting.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-02-03 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 23:48 Guenter Roeck
2015-02-02 10:09 ` Jean Delvare
2015-02-02 10:26 ` Lars-Peter Clausen
2015-02-02 11:56 ` Mark Brown
2015-02-02 14:30 ` Guenter Roeck
2015-02-03 11:42 ` Mark Brown [this message]
2015-02-03 14:21 ` Guenter Roeck
2015-02-03 16:09 ` Mark Brown
2015-02-03 16:58 ` Guenter Roeck
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=20150203114210.GG21293@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.de \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robert.rosengren@axis.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®