From: Rob Herring <robh@kernel.org>
To: Liu Ying <victor.liu@nxp.com>
Cc: devicetree@vger.kernel.org, kernel@pengutronix.de,
marcel.ziswiler@toradex.com, s.hauer@pengutronix.de,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
airlied@linux.ie, robh+dt@kernel.org, linux-imx@nxp.com,
tzimmermann@suse.de, laurentiu.palcu@oss.nxp.com,
guido.gunther@puri.sm, shawnguo@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v9 3/6] dt-bindings: display: imx: Add i.MX8qxp/qm DPR channel binding
Date: Mon, 29 Mar 2021 09:24:00 -0500 [thread overview]
Message-ID: <20210329142400.GA2512413@robh.at.kernel.org> (raw)
In-Reply-To: <1616997446-8783-4-git-send-email-victor.liu@nxp.com>
On Mon, 29 Mar 2021 13:57:23 +0800, Liu Ying wrote:
> This patch adds bindings for i.MX8qxp/qm Display Prefetch Resolve Channel.
>
> Signed-off-by: Liu Ying <victor.liu@nxp.com>
> ---
> v8->v9:
> * Reference 'interrupts-extended' schema instead of 'interrupts' to require
> an additional interrupt(r_rtram_stall) because the reference manual does
> mention it, though the driver doesn't get/use it for now.
> Reference 'interrupt-names' schema to define the two interrupt names -
> 'dpr_wrap' and 'r_rtram_stall'.
> * Drop Rob's R-b tag, as review is needed.
>
> v7->v8:
> * No change.
>
> v6->v7:
> * No change.
>
> v5->v6:
> * No change.
>
> v4->v5:
> * No change.
>
> v3->v4:
> * Improve compatible property by using enum instead of oneOf+const. (Rob)
> * Add Rob's R-b tag.
>
> v2->v3:
> * No change.
>
> v1->v2:
> * Use new dt binding way to add clocks in the example.
>
> .../bindings/display/imx/fsl,imx8qxp-dprc.yaml | 100 +++++++++++++++++++++
> 1 file changed, 100 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/display/imx/fsl,imx8qxp-dprc.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-03-29 14:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 5:57 [PATCH v9 0/6] drm/imx: Introduce i.MX8qm/qxp DPU DRM Liu Ying
2021-03-29 5:57 ` [PATCH v9 1/6] dt-bindings: display: imx: Add i.MX8qxp/qm DPU binding Liu Ying
2021-03-29 5:57 ` [PATCH v9 2/6] dt-bindings: display: imx: Add i.MX8qxp/qm PRG binding Liu Ying
2021-03-29 5:57 ` [PATCH v9 3/6] dt-bindings: display: imx: Add i.MX8qxp/qm DPR channel binding Liu Ying
2021-03-29 14:24 ` Rob Herring [this message]
2021-03-29 5:57 ` [PATCH v9 4/6] drm/atomic: Avoid unused-but-set-variable warning on for_each_old_plane_in_state Liu Ying
2021-03-29 5:57 ` [PATCH v9 5/6] drm/imx: Introduce i.MX8qm/qxp DPU DRM Liu Ying
2021-04-21 11:12 ` Laurentiu Palcu
2021-03-29 5:57 ` [PATCH v9 6/6] MAINTAINERS: add maintainer for i.MX8qxp DPU DRM driver Liu Ying
2021-04-21 11:15 ` Laurentiu Palcu
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=20210329142400.GA2512413@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=guido.gunther@puri.sm \
--cc=kernel@pengutronix.de \
--cc=laurentiu.palcu@oss.nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--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).