From: Philipp Zabel <p.zabel@pengutronix.de>
To: Lucas Stach <l.stach@pengutronix.de>, Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, kernel@pengutronix.de,
dri-devel@lists.freedesktop.org, patchwork-lst@pengutronix.de
Subject: Re: [PATCH v2 1/9] gpu: ipu-v3: add DT binding for the Prefetch Resolve Engine
Date: Mon, 13 Mar 2017 15:45:10 +0100 [thread overview]
Message-ID: <1489416310.2288.73.camel@pengutronix.de> (raw)
In-Reply-To: <20170308111321.3035-1-l.stach@pengutronix.de>
On Wed, 2017-03-08 at 12:13 +0100, Lucas Stach wrote:
> The Prefetch Resolve Engine is a prefetch and tile resolve engine
> which prefetches display data from DRAM to an internal SRAM region.
> It has a single clock for configuration register access and the
> functional units. A single shared interrupt is used for status and
> error signaling.
>
> The only external dependency is the SRAM region to use for the
> prefetch double buffer.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
I have picked up this series. Rob, are you ok with the bindings in this
patch? If so, I'll include it in the next pull request.
regards
Philipp
> ---
> v2:
> - change SRAM phandle to "fsl,iram", as used in other imx DT bindings
> - drop leading 0 in example
> ---
> .../bindings/display/imx/fsl-imx-drm.txt | 26 ++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/display/imx/fsl-imx-drm.txt b/Documentation/devicetree/bindings/display/imx/fsl-imx-drm.txt
> index 971c3eedb1c7..70ae5335d1e3 100644
> --- a/Documentation/devicetree/bindings/display/imx/fsl-imx-drm.txt
> +++ b/Documentation/devicetree/bindings/display/imx/fsl-imx-drm.txt
> @@ -53,6 +53,32 @@ ipu: ipu@18000000 {
> };
> };
>
> +Freescale i.MX PRE (Prefetch Resolve Engine)
> +============================================
> +
> +Required properties:
> +- compatible: should be "fsl,imx6qp-pre"
> +- reg: should be register base and length as documented in the
> + datasheet
> +- clocks : phandle to the PRE axi clock input, as described
> + in Documentation/devicetree/bindings/clock/clock-bindings.txt and
> + Documentation/devicetree/bindings/clock/imx6q-clock.txt.
> +- clock-names: should be "axi"
> +- interrupts: should contain the PRE interrupt
> +- fsl,iram: phandle pointing to the mmio-sram device node, that should be
> + used for the PRE SRAM double buffer.
> +
> +example:
> +
> +pre@21c8000 {
> + compatible = "fsl,imx6qp-pre";
> + reg = <0x021c8000 0x1000>;
> + interrupts = <GIC_SPI 90 IRQ_TYPE_EDGE_RISING>;
> + clocks = <&clks IMX6QDL_CLK_PRE0>;
> + clock-names = "axi";
> + fsl,iram = <&ocram2>;
> +};
> +
> Parallel display support
> ========================
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-03-13 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 11:13 [PATCH v2 1/9] gpu: ipu-v3: add DT binding for the Prefetch Resolve Engine Lucas Stach
2017-03-08 11:13 ` [PATCH v2 2/9] gpu: ipu-v3: add driver for " Lucas Stach
2017-03-08 11:13 ` [PATCH v2 3/9] gpu: ipu-v3: add DT binding for the Prefetch Resolve Gasket Lucas Stach
2017-03-08 11:13 ` [PATCH v2 4/9] gpu: ipu-v3: add driver for " Lucas Stach
2017-03-08 11:13 ` [PATCH v2 5/9] gpu: ipu-v3: document valid IPUv3 compatibles and extend for i.MX6 QuadPlus Lucas Stach
2017-03-08 11:13 ` [PATCH v2 6/9] gpu: ipu-v3: hook up PRG unit Lucas Stach
2017-03-08 11:13 ` [PATCH v2 7/9] gpu: ipu-v3: only set non-zero AXI ID for IC when PRG is absent Lucas Stach
2017-03-08 11:13 ` [PATCH v2 8/9] drm/imx: enable/disable PRG on CRTC enable/disable Lucas Stach
2017-03-08 11:13 ` [PATCH v2 9/9] drm/imx: use PRG/PRE when possible Lucas Stach
2017-03-13 14:45 ` Philipp Zabel [this message]
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=1489416310.2288.73.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=mark.rutland@arm.com \
--cc=patchwork-lst@pengutronix.de \
--cc=robh+dt@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).