From: <kostap@marvell.com>
To: <linux-pm@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <Julia.Lawall@inria.fr>, <amitk@kernel.org>,
<daniel.lezcano@linaro.org>, <rui.zhang@intel.com>,
<miquel.raynal@bootlin.com>, <sboyd@kernel.org>,
<mturquette@baylibre.com>, <mw@semihalf.com>, <jaz@semihalf.com>,
<nadavh@marvell.com>, <stefanc@marvell.com>, <bpeled@marvell.com>,
"Konstantin Porotchkin" <kostap@marvell.com>
Subject: [PATCH 0/2] Enable usage of Marvell FW SIP services
Date: Thu, 11 Feb 2021 15:48:50 +0200 [thread overview]
Message-ID: <20210211134852.23648-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
v3:
* fix build errors and rebase on clk-next branch
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 | 174 ++++++++++++++++++--
drivers/thermal/armada_thermal.c | 125 +++++++++++++-
include/soc/marvell/armada8k/fw.h | 22 +++
3 files changed, 302 insertions(+), 19 deletions(-)
create mode 100644 include/soc/marvell/armada8k/fw.h
--
2.17.1
next reply other threads:[~2021-02-11 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 13:48 kostap [this message]
2021-02-11 13:48 ` [PATCH 1/2] thermal: armada: ap806: use firmware SiP services for thermal operations kostap
2021-02-11 13:48 ` [PATCH 2/2] clk: mvebu: use firmware SiP service for accessing dfx register set kostap
-- strict thread matches above, loose matches on Subject: below --
2020-12-17 17:46 [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=20210211134852.23648-1-kostap@marvell.com \
--to=kostap@marvell.com \
--cc=Julia.Lawall@inria.fr \
--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-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.