From: Kevin Tang <kevin3.tang@gmail.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
David Airlie <airlied@linux.ie>,
Lyra Zhang <zhang.lyra@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Orson Zhai <orsonzhai@gmail.com>, Sean Paul <sean@poorly.run>
Subject: Re: [PATCH 5/6] dt-bindings: display: add Unisoc's mipi dsi&dphy bindings
Date: Tue, 1 Dec 2020 21:56:32 +0800 [thread overview]
Message-ID: <CAFPSGXYwHyF7xEpc-OiVtpSOKiorRO=jGGftKArK-NeGDGMvdw@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqKZKZtOaduTEuu2dgD9sFf5YDvcSkQfBVA9Ssn4n_mDsg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 6149 bytes --]
Hi Rob,
Rob Herring <robh+dt@kernel.org> 于2020年12月1日周二 上午4:31写道:
> On Mon, Nov 30, 2020 at 7:29 AM Kevin Tang <kevin3.tang@gmail.com> wrote:
> >
> > From: Kevin Tang <kevin.tang@unisoc.com>
> >
> > Adds MIPI DSI Master and MIPI DSI-PHY (D-PHY)
> > support for Unisoc's display subsystem.
> >
> > Cc: Orson Zhai <orsonzhai@gmail.com>
> > Cc: Chunyan Zhang <zhang.lyra@gmail.com>
> > Signed-off-by: Kevin Tang <kevin.tang@unisoc.com>
> > ---
> > .../display/sprd/sprd,sharkl3-dsi-host.yaml | 107
> +++++++++++++++++++++
> > .../display/sprd/sprd,sharkl3-dsi-phy.yaml | 84
> ++++++++++++++++
> > 2 files changed, 191 insertions(+)
> > create mode 100644
> Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dsi-host.yaml
> > create mode 100644
> Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dsi-phy.yaml
> >
> > diff --git
> a/Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dsi-host.yaml
> b/Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dsi-host.yaml
> > new file mode 100644
> > index 0000000..fe0e89d
> > --- /dev/null
> > +++
> b/Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dsi-host.yaml
> > @@ -0,0 +1,107 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id:
> http://devicetree.org/schemas/display/sprd/sprd,sharkl3-dsi-host.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Unisoc MIPI DSI Controller
> > +
> > +maintainers:
> > + - Kevin Tang <kevin.tang@unisoc.com>
> > +
> > +properties:
> > + compatible:
> > + const: sprd,sharkl3-dsi-host
> > +
> > + reg:
> > + maxItems: 1
> > + description:
> > + Physical base address and length of the registers set for the
> device.
> > +
> > + interrupts:
> > + maxItems: 2
> > + description:
> > + Should contain DSI interrupt.
> > +
> > + clocks:
> > + minItems: 1
> > +
> > + clock-names:
> > + items:
> > + - const: clk_src_96m
> > +
> > + power-domains:
> > + maxItems: 1
> > + description: A phandle to DSIM power domain node
> > +
> > + ports:
> > + type: object
> > +
> > + properties:
> > + "#address-cells":
> > + const: 1
> > +
> > + "#size-cells":
> > + const: 0
> > +
> > + port@0:
> > + type: object
> > + description:
> > + A port node with endpoint definitions as defined in
> > + Documentation/devicetree/bindings/media/video-interfaces.txt.
> > + That port should be the input endpoint, usually coming from
> > + the associated DPU.
> > + port@1:
> > + type: object
> > + description:
> > + A port node with endpoint definitions as defined in
> > + Documentation/devicetree/bindings/media/video-interfaces.txt.
> > + That port should be the output endpoint, usually output to
> > + the associated DPHY.
> > +
> > + required:
> > + - "#address-cells"
> > + - "#size-cells"
> > + - port@0
> > + - port@1
> > +
> > + additionalProperties: false
> > +
> > +required:
> > + - compatible
> > + - reg
> > + - interrupts
> > + - clocks
> > + - clock-names
> > + - ports
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + #include <dt-bindings/interrupt-controller/arm-gic.h>
> > + #include <dt-bindings/clock/sprd,sc9860-clk.h>
> > + dsi: dsi@63100000 {
> > + compatible = "sprd,sharkl3-dsi-host";
> > + reg = <0x63100000 0x1000>;
> > + interrupts = <GIC_SPI 48 IRQ_TYPE_LEVEL_HIGH>,
> > + <GIC_SPI 49 IRQ_TYPE_LEVEL_HIGH>;
> > + clock-names = "clk_src_96m";
> > + clocks = <&pll CLK_TWPLL_96M>;
> > + ports {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + port@0 {
> > + reg = <0>;
> > + dsi_in: endpoint {
> > + remote-endpoint = <&dpu_out>;
> > + };
> > + };
> > + port@1 {
> > + reg = <1>;
> > + dsi_out: endpoint {
> > + remote-endpoint = <&dphy_in>;
> > + };
> > + };
> > + };
> > + };
> > diff --git
> a/Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dsi-phy.yaml
> b/Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dsi-phy.yaml
> > new file mode 100644
> > index 0000000..b4715d5
> > --- /dev/null
> > +++
> b/Documentation/devicetree/bindings/display/sprd/sprd,sharkl3-dsi-phy.yaml
> > @@ -0,0 +1,84 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id:
> http://devicetree.org/schemas/display/sprd/sprd,sharkl3-dsi-phy.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Unisoc MIPI DSI-PHY (D-PHY)
> > +
> > +maintainers:
> > + - Kevin Tang <kevin.tang@unisoc.com>
> > +
> > +properties:
> > + compatible:
> > + const: sprd,sharkl3-dsi-phy
> > +
> > + reg:
> > + maxItems: 1
> > + description:
> > + Must be the dsi controller base address.
> > +
> > + ports:
> > + type: object
> > +
> > + properties:
> > + "#address-cells":
> > + const: 1
> > +
> > + "#size-cells":
> > + const: 0
> > +
> > + port@0:
> > + type: object
> > + description:
> > + A port node with endpoint definitions as defined in
> > + Documentation/devicetree/bindings/media/video-interfaces.txt.
> > + That port should be the output endpoint, usually output to
> > + the associated panel.
> > + port@1:
>
> For PHYs, we use the PHY binding, not the graph binding. Please follow
> what practically every other DSI PHY does.
>
It seems that the dphy driver does not need to exist alone, so i remove
dphy and dsi graph binding, merge the dphy driver into the dsi driver.
>
> Rob
>
[-- Attachment #1.2: Type: text/html, Size: 8921 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-12-02 8:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 14:28 [PATCH 0/6] Add Unisoc's drm kms module Kevin Tang
2020-11-30 14:28 ` [PATCH 1/6] dt-bindings: display: add Unisoc's drm master bindings Kevin Tang
2020-11-30 20:29 ` Rob Herring
2020-12-01 7:36 ` Kevin Tang
2020-12-01 17:36 ` Rob Herring
2020-11-30 14:28 ` [PATCH 2/6] drm/sprd: add Unisoc's drm kms master Kevin Tang
2020-11-30 14:28 ` [PATCH 3/6] dt-bindings: display: add Unisoc's dpu bindings Kevin Tang
2020-11-30 14:28 ` [PATCH 4/6] drm/sprd: add Unisoc's drm display controller driver Kevin Tang
2020-11-30 14:28 ` [PATCH 5/6] dt-bindings: display: add Unisoc's mipi dsi&dphy bindings Kevin Tang
2020-11-30 20:31 ` Rob Herring
2020-12-01 13:56 ` Kevin Tang [this message]
2020-12-01 17:34 ` Rob Herring
2020-11-30 14:28 ` [PATCH 6/6] drm/sprd: add Unisoc's drm mipi dsi&dphy driver Kevin Tang
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='CAFPSGXYwHyF7xEpc-OiVtpSOKiorRO=jGGftKArK-NeGDGMvdw@mail.gmail.com' \
--to=kevin3.tang@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=orsonzhai@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean@poorly.run \
--cc=zhang.lyra@gmail.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).