From: Thor Thayer <thor.thayer@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RFC: Using regmap in ARM64 for EL3 register access
Date: Thu, 29 Mar 2018 18:00:30 -0500 [thread overview]
Message-ID: <0cf26fec-a702-9d57-c7e0-85064690133c@linux.intel.com> (raw)
Hi,
I'm working on an ARM64 architecture that needs to manipulate some
protected registers that are only accessible in EL3. Linux is running at
EL1 which doesn't have the proper permissions for these registers.
Since U-Boot is running at the higher EL3, we communicate to the U-Boot
functions through a SMC mechanism.
The regmap framework seems like a good match for accessing these
registers. We need the same functionality as I2C and SPI regmaps - read,
write, and update registers.
Any comments or suggestions about using regmap for this purpose? Is
there a better method?
Thanks,
Thor
next reply other threads:[~2018-03-29 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 23:00 Thor Thayer [this message]
2018-04-04 10:47 ` RFC: Using regmap in ARM64 for EL3 register access Sudeep Holla
2018-04-04 18:18 ` Thor Thayer
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=0cf26fec-a702-9d57-c7e0-85064690133c@linux.intel.com \
--to=thor.thayer@linux.intel.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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