From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Liu Ying <victor.liu@nxp.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
saravanak@google.com, gregkh@linuxfoundation.org,
geert+renesas@glider.be
Subject: Re: [PATCH 3/3] dt-bindings: bus: Add Freescale i.MX8qxp pixel link MSI bus binding
Date: Tue, 2 Aug 2022 13:04:14 +0200 [thread overview]
Message-ID: <8f04b8c8-620c-3b32-ce4a-2d4b1aa484d9@linaro.org> (raw)
In-Reply-To: <20220802071310.2650864-4-victor.liu@nxp.com>
On 02/08/2022 09:13, Liu Ying wrote:
> Freescale i.MX8qxp pixel link MSI bus is a simple memory-mapped bus.
> It is used to access peripherals in i.MX8qm/qxp imaging, LVDS, MIPI
> DSI and HDMI TX subsystems, like I2C controller, PWM controller,
> MIPI DSI controller and Control and Status Registers (CSR) module.
>
> Reference simple-pm-bus bindings and add Freescale i.MX8qxp pixel
> link MSI bus specific bindings.
>
> Signed-off-by: Liu Ying <victor.liu@nxp.com>
> ---
> .../bus/fsl,imx8qxp-pixel-link-msi-bus.yaml | 84 +++++++++++++++++++
> 1 file changed, 84 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/bus/fsl,imx8qxp-pixel-link-msi-bus.yaml
>
> diff --git a/Documentation/devicetree/bindings/bus/fsl,imx8qxp-pixel-link-msi-bus.yaml b/Documentation/devicetree/bindings/bus/fsl,imx8qxp-pixel-link-msi-bus.yaml
> new file mode 100644
> index 000000000000..24f50535f5c2
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/bus/fsl,imx8qxp-pixel-link-msi-bus.yaml
> @@ -0,0 +1,84 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/bus/fsl,imx8qxp-pixel-link-msi-bus.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Freescale i.MX8qxp Pixel Link Medium Speed Interconnect (MSI) Bus
Shouldn't this be interconnect, not a bus? Not only located in
interconnect directory but actually being proper interconnect? Although
you mentioned that the firmware controls it, so maybe that would explain
this being only a resource provider.
You should be sure of it, because later if you want to add proper
interconnect properties (e.g. bandwidth voting, paths) *you will not be
able*. Ever.
> +
> +maintainers:
> + - Liu Ying <victor.liu@nxp.com>
> +
> +description: |
> + i.MX8qxp pixel link MSI bus is used to control settings of PHYs, I/Os
> + sitting together with the PHYs. It is not the same as the MSI bus coming
> + from i.MX8 System Controller Unit (SCU) which is used to control power,
> + clock and reset through the i.MX8 Distributed Slave System Controller (DSC).
> +
> + i.MX8qxp pixel link MSI bus is a simple memory-mapped bus. Two input clocks,
> + that is, MSI clock and AHB clock, need to be enabled so that peripherals
> + connected to the bus can be accessed. Also, the bus is part of a power
> + domain. The power domain needs to be enabled before the peripherals can
> + be accessed.
> +
> + Peripherals in i.MX8qm/qxp imaging, LVDS, MIPI DSI and HDMI TX subsystems,
> + like I2C controller, PWM controller, MIPI DSI controller and Control and
> + Status Registers (CSR) module, are accessed through the bus.
> +
> + The i.MX System Controller Firmware (SCFW) owns and uses the i.MX8qm/qxp
> + pixel link MSI bus controller and does not allow SCFW user to control it.
> + So, the controller's registers cannot be accessed by SCFW user. Hence,
> + the interrupts generated by the controller don't make any sense from SCFW
> + user's point of view.
> +
> +allOf:
> + - $ref: simple-pm-bus.yaml#
> +
> +properties:
> + compatible:
> + items:
> + - enum:
> + - fsl,imx8qxp-display-pixel-link-msi-bus
> + - fsl,imx8qm-display-pixel-link-msi-bus
> + - {} # simple-pm-bus, but not listed here to avoid false select
simple-pm-bus must be here. You need to sort out the select instead,
just like we do it for other devices (e.g. primecell).
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + items:
> + - description: master gated clock from system
> + - description: AHB clock
> +
> + clock-names:
> + items:
> + - const: msi
> + - const: ahb
> +
> +required:
compatible and reg as well.
> + - clocks
> + - clock-names
> + - power-domains
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/imx8-lpcg.h>
> + #include <dt-bindings/firmware/imx/rsrc.h>
> + bus@56200000 {
> + compatible = "fsl,imx8qxp-display-pixel-link-msi-bus", "simple-pm-bus";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + reg = <0x56200000 0x20000>;
put reg just after compatible.
> + interrupt-parent = <&dc0_irqsteer>;
> + interrupts = <320>;
> + ranges;
> + clocks = <&dc0_disp_ctrl_link_mst0_lpcg IMX_LPCG_CLK_4>,
> + <&dc0_disp_ctrl_link_mst0_lpcg IMX_LPCG_CLK_4>;
> + clock-names = "msi", "ahb";
> + power-domains = <&pd IMX_SC_R_DC_0>;
> + };
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-08-02 11:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 7:13 [PATCH 0/3] drivers: bus: Add Freescale i.MX8qxp pixel link MSI bus support Liu Ying
2022-08-02 7:13 ` [PATCH 1/3] drivers: bus: simple-pm-bus: Populate simple MFD child devices Liu Ying
2022-08-02 7:13 ` [PATCH 2/3] drivers: bus: simple-pm-bus: Use clocks Liu Ying
2022-08-02 10:56 ` Krzysztof Kozlowski
2022-08-02 10:59 ` Krzysztof Kozlowski
2022-08-02 7:13 ` [PATCH 3/3] dt-bindings: bus: Add Freescale i.MX8qxp pixel link MSI bus binding Liu Ying
2022-08-02 11:04 ` Krzysztof Kozlowski [this message]
2022-08-02 15:47 ` Liu Ying
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=8f04b8c8-620c-3b32-ce4a-2d4b1aa484d9@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=saravanak@google.com \
--cc=shawnguo@kernel.org \
--cc=victor.liu@nxp.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;
as well as URLs for NNTP newsgroup(s).