devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: michael.srba@seznam.cz
To: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>
Cc: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Saravana Kannan <saravanak@google.com>,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org, Michael Srba <Michael.Srba@seznam.cz>
Subject: [RESEND v9 0/5] enable use of resources on the SSC bus on (some) qcom SoCs
Date: Mon, 11 Apr 2022 09:21:51 +0200	[thread overview]
Message-ID: <20220411072156.24451-1-michael.srba@seznam.cz> (raw)

From: Michael Srba <Michael.Srba@seznam.cz>

NOTE: previous versions of this series didn't use a cover letter,
it's added in this resend in order to not upset the kernel bot.

This series adds necessary changes for accessing recources in the SSC block
on msm8998 (though it should be possible to extend this to support other
SoCs).

In order to make use of these changes, Linux (HLOS in qcom's terms) needs
to be allowed to access the relevant address ranges by the SMMU
configuration.

For a simple way to modify an existing (closed source) qcom hypervisor
image to change the static SMMU configuration, see [1].

If you lack ownership of your device, it should alternatively be possible
to change the SMMU configuration at a later point, provided you manage to
get code execution in the hypervisor by way of an exploit.

[1] https://michael-srba.cz/mainline4life/msm8998_hypervisor_patch.html

Michael Srba (5):
  dt-bindings: clock: gcc-msm8998: Add definitions of SSC-related clocks
  clk: qcom: gcc-msm8998: add SSC-related clocks
  dt-bindings: bus: add device tree bindings for qcom,ssc-block-bus
  drivers: bus: add driver for initializing the SSC bus on (some) qcom
    SoCs
  arm64: dts: qcom: msm8998: reserve potentially inaccessible clocks

 .../bindings/bus/qcom,ssc-block-bus.yaml      | 147 +++++++
 arch/arm64/boot/dts/qcom/msm8998.dtsi         |  15 +
 drivers/bus/Kconfig                           |  11 +
 drivers/bus/Makefile                          |   1 +
 drivers/bus/qcom-ssc-block-bus.c              | 391 ++++++++++++++++++
 drivers/clk/qcom/gcc-msm8998.c                |  56 +++
 include/dt-bindings/clock/qcom,gcc-msm8998.h  |   4 +
 7 files changed, 625 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/bus/qcom,ssc-block-bus.yaml
 create mode 100644 drivers/bus/qcom-ssc-block-bus.c

-- 
2.35.1


             reply	other threads:[~2022-04-11  7:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11  7:21 michael.srba [this message]
2022-04-11  7:21 ` [RESEND v9 1/5] dt-bindings: clock: gcc-msm8998: Add definitions of SSC-related clocks michael.srba
2022-04-11  7:21 ` [RESEND v9 2/5] clk: qcom: gcc-msm8998: add " michael.srba
2022-04-11  7:21 ` [RESEND v9 3/5] dt-bindings: bus: add device tree bindings for qcom,ssc-block-bus michael.srba
2022-04-11  7:21 ` [RESEND v9 4/5] drivers: bus: add driver for initializing the SSC bus on (some) qcom SoCs michael.srba
2022-04-11  7:21 ` [RESEND v9 5/5] arm64: dts: qcom: msm8998: reserve potentially inaccessible clocks michael.srba
2022-04-21 14:27 ` (subset) [RESEND v9 0/5] enable use of resources on the SSC bus on (some) qcom SoCs Bjorn Andersson

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=20220411072156.24451-1-michael.srba@seznam.cz \
    --to=michael.srba@seznam.cz \
    --cc=agross@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jeffrey.l.hugo@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=saravanak@google.com \
    --cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).