devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Liu Ying <victor.liu@nxp.com>,
	dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Cc: p.zabel@pengutronix.de, airlied@gmail.com, daniel@ffwll.ch,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	tzimmermann@suse.de, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
	kernel@pengutronix.de, festevam@gmail.com, tglx@linutronix.de
Subject: Re: [PATCH 05/10] dt-bindings: display: imx: Add i.MX8qxp Display Controller
Date: Sun, 7 Jul 2024 16:03:58 +0200	[thread overview]
Message-ID: <e2454904-c70e-49f9-b7b6-05ef348c35fb@kernel.org> (raw)
In-Reply-To: <20240705090932.1880496-6-victor.liu@nxp.com>

On 05/07/2024 11:09, Liu Ying wrote:
> i.MX8qxp Display Controller(DC) is comprised of three main components that
> include a blit engine for 2D graphics accelerations, display controller for
> display output processing, as well as a command sequencer.
> 
> Signed-off-by: Liu Ying <victor.liu@nxp.com>
> ---
>  .../bindings/display/imx/fsl,imx8qxp-dc.yaml  | 243 ++++++++++++++++++
>  1 file changed, 243 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/display/imx/fsl,imx8qxp-dc.yaml
> 
> diff --git a/Documentation/devicetree/bindings/display/imx/fsl,imx8qxp-dc.yaml b/Documentation/devicetree/bindings/display/imx/fsl,imx8qxp-dc.yaml
> new file mode 100644
> index 000000000000..a2ad280d2839
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/imx/fsl,imx8qxp-dc.yaml
> @@ -0,0 +1,243 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/display/imx/fsl,imx8qxp-dc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Freescale i.MX8qxp Display Controller
> +
> +description: |
> +  The Freescale i.MX8qxp Display Controller(DC) is comprised of three main
> +  components that include a blit engine for 2D graphics accelerations, display
> +  controller for display output processing, as well as a command sequencer.
> +
> +                                  Display buffers              Source buffers
> +                                 (AXI read master)            (AXI read master)
> +                                  | .......... |                  | | |
> +      +---------------------------+------------+------------------+-+-+------+
> +      | Display Controller (DC)   | .......... |                  | | |      |
> +      |                           |            |                  | | |      |
> +      |   @@@@@@@@@@@  +----------+------------+------------+     | | |      |
> +  A   |  | Command   | |          V            V            |     | | |      |
> +  X <-+->| Sequencer | |    @@@@@@@@@@@@@@@@@@@@@@@@@@@@    |     V V V      |
> +  I   |  | (AXI CLK) | |   |                            |   |   @@@@@@@@@@   |
> +      |   @@@@@@@@@@@  |   |       Pixel Engine         |   |  |          |  |
> +      |       |        |   |         (AXI CLK)          |   |  |          |  |
> +      |       V        |    @@@@@@@@@@@@@@@@@@@@@@@@@@@@    |  |          |  |
> +  A   |   ***********  |       |   |            |   |       |  |   Blit   |  |
> +  H <-+->| Configure | |       V   V            V   V       |  |  Engine  |  |
> +  B   |  | (CFG CLK) | |    00000000000      11111111111    |  | (AXI CLK)|  |
> +      |   ***********  |   |  Display  |    |  Display  |   |  |          |  |
> +      |                |   |  Engine   |    |  Engine   |   |  |          |  |
> +      |                |   | (Disp CLK)|    | (Disp CLK)|   |  |          |  |
> +      |   @@@@@@@@@@@  |    00000000000      11111111111    |   @@@@@@@@@@   |
> +  I   |  |  Common   | |         |                |         |       |        |
> +  R <-+--|  Control  | |         |    Display     |         |       |        |
> +  Q   |  | (AXI CLK) | |         |   Controller   |         |       |        |
> +      |   @@@@@@@@@@@  +------------------------------------+       |        |
> +      |                          |                |       ^         |        |
> +      +--------------------------+----------------+-------+---------+--------+
> +              ^                  |                |       |         |
> +              |                  V                V       |         V
> +       Clocks & Resets        Display          Display  Panic   Destination
> +                              Output0          Output1 Control    buffer
> +                                                              (AXI write master)
> +
> +maintainers:
> +  - Liu Ying <victor.liu@nxp.com>
> +
> +properties:
> +  compatible:
> +    const: fsl,imx8qxp-dc
> +
> +  reg:
> +    maxItems: 1
> +
> +  clocks:
> +    maxItems: 1
> +
> +  resets:
> +    maxItems: 2
> +
> +  reset-names:
> +    items:
> +      - const: axi
> +      - const: cfg
> +
> +  power-domains:
> +    maxItems: 1
> +
> +  "#address-cells":
> +    const: 1
> +
> +  "#size-cells":
> +    const: 1
> +
> +  ranges: true
> +
> +patternProperties:
> +  "^axi-performance-counter@[0-9a-f]+$":

Node names should be generic. See also an explanation and list of
examples (not exhaustive) in DT specification:
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation


Is this a PMU?

> +    type: object
> +    additionalProperties: true
> +
> +    properties:
> +      compatible:
> +        const: fsl,imx8qxp-dc-axi-performance-counter
> +


> +        pixel-engine@56180800 {
> +            compatible = "fsl,imx8qxp-dc-pixel-engine";
> +            reg = <0x56180800 0xac00>;
> +            clocks = <&dc0_lpcg IMX_LPCG_CLK_5>;
> +            #address-cells = <1>;
> +            #size-cells = <1>;
> +            ranges;
> +        };
> +
> +        display-engine@5618b400 {
> +            compatible = "fsl,imx8qxp-dc-display-engine";
> +            reg = <0x5618b400 0x14>, <0x5618b800 0x1c00>;
> +            reg-names = "top", "cfg";
> +            interrupt-parent = <&dc0_intc>;

Where is this node?

I think this proves that interrupt controller is part of the display
controller.

Best regards,
Krzysztof


  reply	other threads:[~2024-07-07 14:04 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-05  9:09 [PATCH 00/10] Add Freescale i.MX8qxp Display Controller support Liu Ying
2024-07-05  9:09 ` [PATCH 01/10] dt-bindings: display: imx: Add some i.MX8qxp Display Controller processing units Liu Ying
2024-07-07 13:58   ` Krzysztof Kozlowski
2024-07-08  6:30     ` Liu Ying
2024-07-08 20:04       ` Rob Herring
2024-07-09  7:36         ` Liu Ying
2024-07-05  9:09 ` [PATCH 02/10] dt-bindings: display: imx: Add i.MX8qxp Display Controller display engine Liu Ying
2024-07-07 13:59   ` Krzysztof Kozlowski
2024-07-08  6:40     ` Liu Ying
2024-07-08 14:04       ` Krzysztof Kozlowski
2024-07-08 14:52         ` Maxime Ripard
2024-07-09  6:50           ` Krzysztof Kozlowski
2024-07-18 15:53             ` Maxime Ripard
2024-07-05  9:09 ` [PATCH 03/10] dt-bindings: display: imx: Add i.MX8qxp Display Controller pixel engine Liu Ying
2024-07-07 14:02   ` Krzysztof Kozlowski
2024-07-08  6:47     ` Liu Ying
2024-07-08 14:05       ` Krzysztof Kozlowski
2024-07-09  6:50         ` Liu Ying
2024-07-05  9:09 ` [PATCH 04/10] dt-bindings: interrupt-controller: Add i.MX8qxp Display Controller interrupt controller Liu Ying
2024-07-07 14:01   ` Krzysztof Kozlowski
2024-07-08  6:51     ` Liu Ying
2024-07-08 14:09       ` Krzysztof Kozlowski
2024-07-09  7:05         ` Liu Ying
2024-07-05  9:09 ` [PATCH 05/10] dt-bindings: display: imx: Add i.MX8qxp Display Controller Liu Ying
2024-07-07 14:03   ` Krzysztof Kozlowski [this message]
2024-07-08  7:01     ` Liu Ying
2024-07-05  9:09 ` [PATCH 06/10] drm/imx: Add i.MX8qxp Display Controller display engine Liu Ying
2024-07-05  9:09 ` [PATCH 07/10] drm/imx: Add i.MX8qxp Display Controller pixel engine Liu Ying
2024-07-05  9:09 ` [PATCH 08/10] drm/imx: Add i.MX8qxp Display Controller interrupt controller Liu Ying
2024-07-05  9:09 ` [PATCH 09/10] drm/imx: Add i.MX8qxp Display Controller KMS Liu Ying
2024-07-07 19:16   ` Markus Elfring
2024-07-08  6:21     ` Liu Ying
2024-07-08  7:09       ` [09/10] " Markus Elfring
2024-07-08  7:33         ` Krzysztof Kozlowski
2024-07-05  9:09 ` [PATCH 10/10] MAINTAINERS: Add maintainer for i.MX8qxp Display Controller Liu Ying
2024-07-05 19:02   ` Frank Li
2024-07-08  6:14     ` Liu Ying
2024-07-05 12:57 ` [PATCH 00/10] Add Freescale i.MX8qxp Display Controller support Francesco Dolcini
2024-07-08  7:03   ` 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=e2454904-c70e-49f9-b7b6-05ef348c35fb@kernel.org \
    --to=krzk@kernel.org \
    --cc=airlied@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tzimmermann@suse.de \
    --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).