From: Mark Brown <broonie@kernel.org>
To: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: regmap: mmio: regression in pre-v4.6-rc1
Date: Wed, 23 Mar 2016 10:34:15 +0000 [thread overview]
Message-ID: <20160323103415.GG2566@sirena.org.uk> (raw)
In-Reply-To: <1981840.HVGTg07J9M@ws-stein>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
On Wed, Mar 23, 2016 at 09:48:42AM +0100, Alexander Stein wrote:
Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns. Doing this makes your messages much
easier to read and reply to.
> 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.
> 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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-23 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 8:48 Alexander Stein
2016-03-23 9:43 ` Alexander Stein
2016-03-23 10:34 ` Mark Brown [this message]
2016-03-23 11:16 ` Alexander Stein
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=20160323103415.GG2566@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexander.stein@systec-electronic.com \
--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
all inboxes | Powered by JetHome®