mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: Mark Brown <broonie@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: mmio: Fix value endianness selection
Date: Mon, 28 Mar 2016 23:11:09 -0700	[thread overview]
Message-ID: <8f62d6ec611e646449ed6fbba197c6f1@agner.ch> (raw)
In-Reply-To: <2467072.5nNY07Ee9z@ws-stein>

On 2016-03-28 23:10, Alexander Stein wrote:
> On Friday 25 March 2016 11:24:59, Mark Brown wrote:
>> On Wed, Mar 23, 2016 at 03:20:46PM +0100, Alexander Stein wrote:
>> > The difference in those drivers is that syscon manually sets
>> > config.val_format_endian before calling regmap_init_mmio.
>> > spi-fsl-dspi does not. I guess this driver relies on this configuration
>> > being done in regmap_get_val_endian. But this is never reached because
>> > after setting
>> Does this IP exist in configurations where it is anything other than big
>> endian?  If not then this probably shouldn't be in DT.
> 
> AFAIK it is included once or twice in the VFxxx series. CC'ed Stefan Agner for 
> confirmation.
> Stefan: Is the DCU on VFxxx attached little-endian, e.g. no byte swapping 
> needed when accessing the periphery?

Yes, DCU as well as DSPI is attached little endian on Vybrid (aka.
vf610).

--
Stefan

      reply	other threads:[~2016-03-29  6:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 13:17 Mark Brown
2016-03-23 13:38 ` Alexander Stein
2016-03-23 13:42 ` Applied "regmap: mmio: Fix value endianness selection" to the regmap tree Mark Brown
2016-03-23 14:20 ` [PATCH] regmap: mmio: Fix value endianness selection Alexander Stein
2016-03-25 11:24   ` Mark Brown
2016-03-29  6:10     ` Alexander Stein
2016-03-29  6:11       ` Stefan Agner [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=8f62d6ec611e646449ed6fbba197c6f1@agner.ch \
    --to=stefan@agner.ch \
    --cc=alexander.stein@systec-electronic.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

Powered by JetHome