From: Changhuang Liang <changhuang.liang@starfivetech.com>
To: Rob Herring <robh@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Conor Dooley <conor@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Philipp Zabel <p.zabel@pengutronix.de>,
Jack Zhu <jack.zhu@starfivetech.com>,
<linux-phy@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v1 2/4] dt-bindings: phy: Add starfive,jh7110-dphy-rx
Date: Mon, 13 Feb 2023 15:51:58 +0800 [thread overview]
Message-ID: <36d8a648-49f4-281e-3947-cf2cbf3827b2@starfivetech.com> (raw)
In-Reply-To: <20230210182935.GA2914589-robh@kernel.org>
On 2023/2/11 2:29, Rob Herring wrote:
> On Thu, Feb 09, 2023 at 10:17:11PM -0800, Changhuang Liang wrote:
>> Starfive SoC like the jh7110 use a MIPI D-PHY RX controller based on
>> a M31 IP. Add a binding for it.
>>
>> Signed-off-by: Changhuang Liang <changhuang.liang@starfivetech.com>
>> ---
>> .../bindings/phy/starfive,jh7110-dphy-rx.yaml | 78 +++++++++++++++++++
>> 1 file changed, 78 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/phy/starfive,jh7110-dphy-rx.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/phy/starfive,jh7110-dphy-rx.yaml b/Documentation/devicetree/bindings/phy/starfive,jh7110-dphy-rx.yaml
>> new file mode 100644
>> index 000000000000..1c1e5c7cbee2
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/phy/starfive,jh7110-dphy-rx.yaml
>> @@ -0,0 +1,78 @@
>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/phy/starfive,jh7110-dphy-rx.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Starfive SoC MIPI D-PHY Rx Controller
>> +
>> +maintainers:
>> + - Jack Zhu <jack.zhu@starfivetech.com>
>> + - Changhuang Liang <changhuang.liang@starfivetech.com>
>> +
>> +description: |
>
> Don't need '|'
>
OK, will delete it.
>> + The Starfive SOC has a MIPI CSI D-PHY based on M31 IP use to transfer
>> + the CSI cameras data.
>> +
>> +properties:
>> + compatible:
>> + items:
>> + - const: "starfive,jh7110-dphy-rx"
>
> Drop quotes.
>
OK, will drop quotes
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + clocks:
>> + minItems: 3
>> + maxItems: 3
>
> Just maxItems is enough.
>
OK, will delete minItems.
>> +
>> + clock-names:
>> + items:
>> + - const: cfg
>> + - const: ref
>> + - const: tx
>> +
>> + resets:
>> + minItems: 2
>> + maxItems: 2
>
> Need to define what each reset is.
>
OK, will define resets.
>> +
>> + starfive,aon-syscon:
>> + $ref: '/schemas/types.yaml#/definitions/phandle-array'
>
> Drop quotes.
>
OK, will drop quote
>> + items:
>> + items:
>> + - description: phandle of AON SYSCON
>> + - description: register offset
>> + description: The register of dphy rx driver can be configured
>> + by AON SYSCON in this property.
>> +
>> + "#phy-cells":
>> + const: 0
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - clocks
>> + - clock-names
>> + - resets
>> + - starfive,aon-syscon
>> + - "#phy-cells"
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/clock/starfive,jh7110-crg.h>
>> + #include <dt-bindings/reset/starfive,jh7110-crg.h>
>> +
>> + dphy@19820000 {
>> + compatible = "starfive,jh7110-dphy-rx";
>> + reg = <0x19820000 0x10000>;
>> + clocks = <&ispcrg JH7110_ISPCLK_M31DPHY_CFGCLK_IN>,
>> + <&ispcrg JH7110_ISPCLK_M31DPHY_REFCLK_IN>,
>> + <&ispcrg JH7110_ISPCLK_M31DPHY_TXCLKESC_LAN0>;
>> + clock-names = "cfg", "ref", "tx";
>> + resets = <&ispcrg JH7110_ISPRST_M31DPHY_HW>,
>> + <&ispcrg JH7110_ISPRST_M31DPHY_B09_ALWAYS_ON>;
>> + starfive,aon-syscon = <&aon_syscon 0x00>;
>> + #phy-cells = <0>;
>> + };
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2023-02-13 7:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 6:17 [PATCH v1 0/4] Add JH7110 MIPI DPHY RX support Changhuang Liang
2023-02-10 6:17 ` [PATCH v1 1/4] riscv: dts: starfive: jh7110: Add aon syscon node Changhuang Liang
2023-02-13 9:28 ` Krzysztof Kozlowski
2023-02-14 2:18 ` Changhuang Liang
2023-02-10 6:17 ` [PATCH v1 2/4] dt-bindings: phy: Add starfive,jh7110-dphy-rx Changhuang Liang
2023-02-10 13:58 ` Rob Herring
2023-02-13 7:47 ` Changhuang Liang
2023-02-10 18:29 ` Rob Herring
2023-02-13 7:51 ` Changhuang Liang [this message]
2023-02-13 9:30 ` Krzysztof Kozlowski
2023-02-14 3:07 ` Changhuang Liang
2023-02-14 7:49 ` Krzysztof Kozlowski
2023-02-15 1:27 ` Changhuang Liang
2023-02-10 6:17 ` [PATCH v1 3/4] phy: starfive: Add mipi dphy rx support Changhuang Liang
2023-02-10 6:17 ` [PATCH v1 4/4] riscv: dts: starfive: Add dphy rx node Changhuang Liang
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=36d8a648-49f4-281e-3947-cf2cbf3827b2@starfivetech.com \
--to=changhuang.liang@starfivetech.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jack.zhu@starfivetech.com \
--cc=kernel@esmil.dk \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=vkoul@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).