From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Rob Herring <robherring2@gmail.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
Will Deacon <will.deacon@arm.com>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v2] coresight-stm: adding driver for CoreSight STM component
Date: Thu, 26 Feb 2015 22:58:53 +0000 [thread overview]
Message-ID: <20150226225853.GM8656@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAL_Jsq+JYc5DBXqEcpJ0O=RdO-uuz_-GR99YsgVqT=uG6CLqJg@mail.gmail.com>
On Thu, Feb 26, 2015 at 04:24:53PM -0600, Rob Herring wrote:
> We really shouldn't do private implementation here. It there really
> any reason not to allow readq/writeq generically for 32-bit or just
> for arm32?
My argument has always been that drivers should do the emulation of
64-bit accesses when there is no native support.
IO registers tend to have side effects when read/written. How do we
know whether the low-half or the high-half should be written first?
This isn't something that an architecture can really dictate. What
may be right for one hardware device may not be correct for another.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2015-02-26 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 23:32 [PATCH v2] coresight-stm: adding driver for CoreSight STM component Mathieu Poirier
2015-02-26 5:53 ` Shawn Guo
2015-02-26 14:22 ` Mathieu Poirier
2015-02-26 22:24 ` Rob Herring
2015-02-26 22:58 ` Russell King - ARM Linux [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=20150226225853.GM8656@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=corbet@lwn.net \
--cc=linux-api@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robherring2@gmail.com \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).