From: Changhuang Liang <changhuang.liang@starfivetech.com>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh+dt@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 v5 1/3] dt-bindings: phy: Add starfive,jh7110-dphy-rx
Date: Tue, 30 May 2023 10:37:50 +0800 [thread overview]
Message-ID: <3b4eff36-28db-5880-3094-efa491a69dc7@starfivetech.com> (raw)
In-Reply-To: <20230529-envy-itinerary-e4007cb0da9a@wendy>
On 2023/5/29 22:05, Conor Dooley wrote:
> Hey Changhuang,
>
> Couple of minor bits from me here, you don't need to fix them unless
> the binding has to change for other reasons.
>
Thanks for your comments.
[...]
>> +$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
>
> nit: either s/SoC/JH7110/ or s/SoC//.
>
Changed to "StarFive JH7110 SoC MIPI D-PHY Rx Controller"?
>> +
>> +maintainers:
>> + - Jack Zhu <jack.zhu@starfivetech.com>
>> + - Changhuang Liang <changhuang.liang@starfivetech.com>
>> +
>> +description:
>> + The StarFive SoC uses the MIPI CSI D-PHY based on M31 IP to transfer
>> + CSI camera data.
>
> nit: "Starfive SoCs contain a MIPI CSI D-PHY based on an M31 IP, used to
> transfer CSI camera data."
>
Will fixed this.
>> +properties:
>> + compatible:
>> + const: starfive,jh7110-dphy-rx
[...]
>> + resets:
>> + items:
>> + - description: DPHY_HW reset
>> + - description: DPHY_B09_ALWAYS_ON reset
>
> I'd prefer not to have what looks like copy-paste from a datasheet
> and instead a description of what they do.
>
> Otherwise, this looks grand to me, but I don't understand the hardware
> so there is no point in me leaving an R-b on this.
> Hopefully Krzysztof can take a look at it in the coming days.
>
I will wait for Krzysztof's comments.
next prev parent reply other threads:[~2023-05-30 2:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 12:15 [PATCH v5 0/3] Add JH7110 MIPI DPHY RX support Changhuang Liang
2023-05-29 12:15 ` [PATCH v5 1/3] dt-bindings: phy: Add starfive,jh7110-dphy-rx Changhuang Liang
2023-05-29 14:05 ` Conor Dooley
2023-05-30 2:37 ` Changhuang Liang [this message]
2023-06-08 20:49 ` Rob Herring
2023-05-29 12:15 ` [PATCH v5 2/3] phy: starfive: Add mipi dphy rx support Changhuang Liang
2023-06-21 12:30 ` Vinod Koul
2023-06-25 2:11 ` Changhuang Liang
2023-05-29 12:15 ` [PATCH v5 3/3] riscv: dts: starfive: Add dphy rx node Changhuang Liang
2023-05-29 14:08 ` [PATCH v5 0/3] Add JH7110 MIPI DPHY RX support Conor Dooley
2023-05-30 1:46 ` Changhuang Liang
2023-06-14 9:14 ` 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=3b4eff36-28db-5880-3094-efa491a69dc7@starfivetech.com \
--to=changhuang.liang@starfivetech.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--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+dt@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
all inboxes | Powered by JetHome®