From: Rob Herring <robh@kernel.org>
To: michael.srba@seznam.cz
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
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
Subject: Re: [PATCH v4 3/5] dt-bindings: bus: add device tree bindings for qcom,ssc-block-bus
Date: Tue, 1 Feb 2022 11:26:30 -0600 [thread overview]
Message-ID: <YfltRkup8QhY2Tar@robh.at.kernel.org> (raw)
In-Reply-To: <20220126183250.11924-3-michael.srba@seznam.cz>
On Wed, Jan 26, 2022 at 07:32:48PM +0100, michael.srba@seznam.cz wrote:
> From: Michael Srba <Michael.Srba@seznam.cz>
>
> This patch adds bindings for the AHB bus which exposes the SCC block in
> the global address space. This bus (and the SSC block itself) is present
> on certain qcom SoCs.
>
> In typical configuration, this bus (as some of the clocks and registers
> that we need to manipulate) is not accessible to the OS, and the
> resources on this bus are indirectly accessed by communicating with a
> hexagon CPU core residing in the SSC block. In this configuration, the
> hypervisor is the one performing the bus initialization for the purposes
> of bringing the haxagon CPU core out of reset.
>
> However, it is possible to change the configuration, in which case this
> binding serves to allow the OS to initialize the bus.
>
> Signed-off-by: Michael Srba <Michael.Srba@seznam.cz>
> ---
> CHANGES:
> - v2: fix issues caught by by dt-schema
> - v3: none
> - v4: address the issues pointed out in the review
> ---
> .../bindings/bus/qcom,ssc-block-bus.yaml | 150 ++++++++++++++++++
> 1 file changed, 150 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/bus/qcom,ssc-block-bus.yaml
>
> diff --git a/Documentation/devicetree/bindings/bus/qcom,ssc-block-bus.yaml b/Documentation/devicetree/bindings/bus/qcom,ssc-block-bus.yaml
> new file mode 100644
> index 000000000000..4bde169b1a19
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/bus/qcom,ssc-block-bus.yaml
> @@ -0,0 +1,150 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/bus/qcom,ssc-block-bus.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: The AHB Bus Providing a Global View of the SSC Block on (some) qcom SoCs
> +
> +maintainers:
> + - Michael Srba <Michael.Srba@seznam.cz>
> +
> +description: |
> + This binding describes the dependencies (clocks, resets, power domains) which
> + need to be turned on in a sequence before communication over the AHB bus
> + becomes possible.
> +
> + Additionally, the reg property is used to pass to the driver the location of
> + two sadly undocumented registers which need to be poked as part of the sequence.
> +
> +properties:
> + compatible:
> + items:
> + - const: qcom,msm8998-ssc-block-bus
> + - const: qcom,ssc-block-bus
> +
> + reg:
> + description: |
> + Shall contain the addresses of the SSCAON_CONFIG0 and SSCAON_CONFIG1
> + registers
> + minItems: 2
> + maxItems: 2
> +
> + reg-names:
> + items:
> + - const: mpm_sscaon_config0
> + - const: mpm_sscaon_config1
> +
> + '#address-cells':
> + enum: [ 1, 2 ]
> +
> + '#size-cells':
> + enum: [ 1, 2 ]
> +
> + ranges: true
> +
> + clocks:
> + minItems: 6
> + maxItems: 6
> +
> + clock-names:
> + items:
> + - const: xo
> + - const: aggre2
> + - const: gcc_im_sleep
> + - const: aggre2_north
> + - const: ssc_xo
> + - const: ssc_ahbs
> +
> + power-domains:
> + description: Power domain phandles for the ssc_cx and ssc_mx power domains
> + minItems: 2
> + maxItems: 2
> +
> + power-domain-names:
> + items:
> + - const: ssc_cx
> + - const: ssc_mx
> +
> + resets:
> + description: |
> + Reset phandles for the ssc_reset and ssc_bcr resets (note: ssc_bcr is the
> + branch control register associated with the ssc_xo and ssc_ahbs clocks)
> + minItems: 2
> + maxItems: 2
> +
> + reset-names:
> + items:
> + - const: ssc_reset
> + - const: ssc_bcr
> +
> + qcom,halt-regs:
> + $ref: /schemas/types.yaml#/definitions/phandle-array
> + description: describes how to locate the ssc AXI halt register
> + items:
> + - items:
> + - description: Phandle reference to a syscon representing TCSR
> + - description: offset for the ssc AXI halt register
> +
> +required:
> + - compatible
> + - reg
> + - reg-names
> + - '#address-cells'
> + - '#size-cells'
> + - ranges
> + - clocks
> + - clock-names
> + - power-domains
> + - power-domain-names
> + - resets
> + - reset-names
> + - qcom,halt-regs
> +
> +additionalProperties: true
To say anything else should be a node:
additionalProperties:
type: object
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/qcom,gcc-msm8998.h>
> + #include <dt-bindings/clock/qcom,rpmcc.h>
> + #include <dt-bindings/power/qcom-rpmpd.h>
> +
> + soc {
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + // devices under this node are physically located in the SSC block, connected to an ssc-internal bus;
> + ssc_ahb_slave: bus@10ac008 {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges;
> +
> + compatible = "qcom,msm8998-ssc-block-bus", "qcom,ssc-block-bus";
> + reg = <0x10ac008 0x4>, <0x10ac010 0x4>;
> + reg-names = "mpm_sscaon_config0", "mpm_sscaon_config1";
> +
> + clocks = <&xo>,
> + <&rpmcc RPM_SMD_AGGR2_NOC_CLK>,
> + <&gcc GCC_IM_SLEEP>,
> + <&gcc AGGRE2_SNOC_NORTH_AXI>,
> + <&gcc SSC_XO>,
> + <&gcc SSC_CNOC_AHBS_CLK>;
> + clock-names = "xo", "aggre2", "gcc_im_sleep", "aggre2_north", "ssc_xo", "ssc_ahbs";
> +
> + resets = <&gcc GCC_SSC_RESET>, <&gcc GCC_SSC_BCR>;
> + reset-names = "ssc_reset", "ssc_bcr";
> +
> + power-domains = <&rpmpd MSM8998_SSCCX>, <&rpmpd MSM8998_SSCMX>;
> + power-domain-names = "ssc_cx", "ssc_mx";
> +
> + qcom,halt-regs = <&tcsr_mutex_regs 0x26000>;
> +
> + ssc_tlmm: pinctrl@5e10000 {
> + compatible = "qcom,msm8998-ssc-tlmm-pinctrl";
If you don't want to define a schema for this, pick another node that
has a schema already.
> + reg = <0x5E10000 0x10000>;
> + gpio-controller;
> + #gpio-cells = <2>;
> + gpio-ranges = <&ssc_tlmm 0 0 20>;
> + };
> + };
> + };
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2022-02-01 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 18:32 [PATCH v4 1/5] dt-bindings: clock: gcc-msm8998: Add definitions of SSC-related clocks michael.srba
2022-01-26 18:32 ` [PATCH v4 2/5] clk: qcom: gcc-msm8998: add " michael.srba
2022-01-26 18:32 ` [PATCH v4 3/5] dt-bindings: bus: add device tree bindings for qcom,ssc-block-bus michael.srba
2022-01-26 22:10 ` Rob Herring
2022-02-01 17:26 ` Rob Herring [this message]
2022-01-26 18:32 ` [PATCH v4 4/5] drivers: bus: add driver for initializing the SSC bus on (some) qcom SoCs michael.srba
2022-01-26 18:32 ` [PATCH v4 5/5] arm64: dts: qcom: msm8998: reserve potentially inaccessible clocks michael.srba
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=YfltRkup8QhY2Tar@robh.at.kernel.org \
--to=robh@kernel.org \
--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=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=michael.srba@seznam.cz \
--cc=p.zabel@pengutronix.de \
--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 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.