From: <kostap@marvell.com>
To: <linux-clk@vger.kernel.org>, <linux-pm@vger.kernel.org>
Cc: <mturquette@baylibre.com>, <sboyd@kernel.org>,
<miquel.raynal@bootlin.com>, <rui.zhang@intel.com>,
<daniel.lezcano@linaro.org>, <amitk@kernel.org>,
<mw@semihalf.com>, <jaz@semihalf.com>, <nadavh@marvell.com>,
<bpeled@marvell.com>, <stefanc@marvell.com>,
Konstantin Porotchkin <kostap@marvell.com>
Subject: [PATCH 0/2] Enable usage of Marvell FW SIP services
Date: Thu, 17 Dec 2020 19:46:00 +0200 [thread overview]
Message-ID: <20201217174602.22212-1-kostap@marvell.com> (raw)
From: Konstantin Porotchkin <kostap@marvell.com>
These patches enable usage of Arm Trusted Firmware SIP services on Marvell
Armada plaforms for acessing system registers that are not normally accessible
from kernel or user space (EL1/EL0), like DFX registers group.
Grzegorz Jaszczyk (2):
thermal: armada: ap806: use firmware SiP services for thermal
operations
clk: mvebu: use firmware SiP service for accessing dfx register set
drivers/clk/mvebu/ap-cpu-clk.c | 141 +++++++++++++++++---
drivers/thermal/armada_thermal.c | 125 ++++++++++++++++-
include/soc/marvell/armada8k/fw.h | 22 +++
3 files changed, 269 insertions(+), 19 deletions(-)
create mode 100644 include/soc/marvell/armada8k/fw.h
--
2.17.1
next reply other threads:[~2020-12-17 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 17:46 kostap [this message]
2020-12-17 17:46 ` [PATCH 1/2] thermal: armada: ap806: use firmware SiP services for thermal operations kostap
2020-12-18 5:27 ` kernel test robot
2020-12-18 7:12 ` kernel test robot
2020-12-17 17:46 ` [PATCH 2/2] clk: mvebu: use firmware SiP service for accessing dfx register set kostap
2020-12-20 0:16 ` Stephen Boyd
2020-12-29 22:51 ` Grzegorz Jaszczyk
-- strict thread matches above, loose matches on Subject: below --
2021-02-11 13:48 [PATCH 0/2] Enable usage of Marvell FW SIP services kostap
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=20201217174602.22212-1-kostap@marvell.com \
--to=kostap@marvell.com \
--cc=amitk@kernel.org \
--cc=bpeled@marvell.com \
--cc=daniel.lezcano@linaro.org \
--cc=jaz@semihalf.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=rui.zhang@intel.com \
--cc=sboyd@kernel.org \
--cc=stefanc@marvell.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