From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: regmap: mmio: regression in pre-v4.6-rc1
Date: Wed, 23 Mar 2016 12:16:13 +0100 [thread overview]
Message-ID: <4116114.XWfjkrStv7@ws-stein> (raw)
In-Reply-To: <20160323103415.GG2566@sirena.org.uk>
On Wednesday 23 March 2016 10:34:15, Mark Brown wrote:
> > I'm currently trying to get PCIe working on LS1021A (little-endian
> > ARM). For link-detection I need access to a syscon perpheral (SCFG)
> > which is attched to CPU as big-endian.
>
> Are you *sure* that this is actually big endian? Are you basing this on
> documentation or on what happened to work for you in the past.
Please refer to QorIQ LS1021A Reference Manual (REV 0) table 2.2 (CCSR block
base address map) which states that this peripheral (among _most_ but not all)
requires byte swapping. Same for DSPI.
Yeah, it sounds strange.
> > Based on current linus's master (a24e3d414e59ac765, "Merge branch
> > 'akpm' (patches from Andrew)") I noticed the access is actually done
> > as little-endian. I could track it down to commit 922a9f936e40001f
> > ("regmap: mmio: Convert to regmap_bus and fix accessor usage").
> > Reverting it, the access is fine now and I get my PCIe link.
>
> Have you tried tracing through the code to see what ends up happening to
> the I/O? It should come out using your architecture's big endian
> accessors.
In regmap_mmio_gen_context ctx->reg_read is set to regmap_mmio_read32le and
ctx->reg_write to regmap_mmio_write32le respectively.
I noticed that before that change map->reg_read = _regmap_bus_read and map-
>reg_write = _regmap_bus_raw_write. After that change it is map->reg_read =
_regmap_bus_reg_read resp. map->reg_write = _regmap_bus_reg_write.
I hope this description is not that confusing.
Best regards,
Alexander
next prev parent reply other threads:[~2016-03-23 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 8:48 regmap: mmio: regression in pre-v4.6-rc1 Alexander Stein
2016-03-23 9:43 ` Alexander Stein
2016-03-23 10:34 ` Mark Brown
2016-03-23 11:16 ` Alexander Stein [this message]
2016-03-23 11:39 ` Mark Brown
2016-03-23 11:50 ` Alexander Stein
2016-03-23 12:05 ` 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=4116114.XWfjkrStv7@ws-stein \
--to=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