From: <kostap@marvell.com>
To: <linux-clk@vger.kernel.org>
Cc: <linux-pm@vger.kernel.org>, <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 v2 0/2] Enable usage of Marvell FW SIP services
Date: Thu, 14 Jan 2021 12:26:41 +0200 [thread overview]
Message-ID: <20210114102643.16108-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 accessing system registers that are not
normally accessible from kernel or user space (EL1/EL0), like DFX
registers group.
v2:
* use separate legacy/smc regmap functions registered at ap-cpu
clock driver probe according to FW response
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 | 168 ++++++++++++++++++--
drivers/thermal/armada_thermal.c | 125 ++++++++++++++-
include/soc/marvell/armada8k/fw.h | 22 +++
3 files changed, 296 insertions(+), 19 deletions(-)
create mode 100644 include/soc/marvell/armada8k/fw.h
--
2.17.1
next reply other threads:[~2021-01-14 10:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 10:26 kostap [this message]
2021-01-14 10:26 ` [PATCH v2 1/2] thermal: armada: ap806: use firmware SiP services for thermal operations kostap
2021-01-14 13:17 ` kernel test robot
2021-01-14 10:26 ` [PATCH v2 2/2] clk: mvebu: use firmware SiP service for accessing dfx register set kostap
2021-02-11 2:36 ` [PATCH v2 0/2] Enable usage of Marvell FW SIP services Stephen Boyd
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=20210114102643.16108-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