From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Nishanth Menon <nm@ti.com>, Kishon Vijay Abraham I <kishon@ti.com>
Cc: devicetree@vger.kernel.org, yamonkar@cadence.com,
Sekhar Nori <nsekhar@ti.com>, Tero Kristo <t-kristo@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Swapnil Jakhade <sjakhade@cadence.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] arm64: dts: ti: k3-j721e-main: add DP & DP PHY
Date: Thu, 17 Sep 2020 16:52:06 +0300 [thread overview]
Message-ID: <933cccf5-fa5c-dc46-36e5-3200e7b7801d@ti.com> (raw)
In-Reply-To: <20200917130723.q3asxcb6uoenady5@akan>
Hi Nishanth,
On 17/09/2020 16:07, Nishanth Menon wrote:
> On 10:12-20200917, Tomi Valkeinen wrote:
>> Add DT nodes for DisplayPort and DisplayPort PHY. The DP is Cadence MHDP
>> 8546 and the PHY is a Cadence Torrent PHY with TI WIZ wrapper.
>>
>> A slight irregularity in the bindings is the DPTX PHY register block,
>> which is in the MHDP IP, but is needed and mapped by the PHY.
>>
>> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
>
> just quick notes below:
>
>> ---
>> arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 104 ++++++++++++++++++++++
>> 1 file changed, 104 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-j721e-main.dtsi b/arch/arm64/boot/dts/ti/k3-j721e-main.dtsi
>> index 12ceea9b3c9a..82d89dd3faf5 100644
>> --- a/arch/arm64/boot/dts/ti/k3-j721e-main.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-j721e-main.dtsi
>> @@ -553,6 +553,82 @@ serdes3: serdes@5030000 {
>> };
>> };
>>
>> + serdes_wiz4: wiz@5050000 {
> serdes-mux ? - I think we might want to cleanup other similar usage
> instead of "wiz" or maybe just "mux"?
>
>> + compatible = "ti,j721e-wiz-10g";
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> + power-domains = <&k3_pds 297 TI_SCI_PD_EXCLUSIVE>;
>> + clocks = <&k3_clks 297 1>, <&k3_clks 297 9>, <&dummy_cmn_refclk>;
>> + clock-names = "fck", "core_ref_clk", "ext_ref_clk";
>> + assigned-clocks = <&k3_clks 297 9>;
>> + assigned-clock-parents = <&k3_clks 297 10>;
>> + assigned-clock-rates = <19200000>;
>> + num-lanes = <4>;
>> + #reset-cells = <1>;
>> + ranges = <0x5050000 0x0 0x5050000 0x10000>,
>> + <0xa030a00 0x0 0xa030a00 0x40>;
>> +
>> + wiz4_pll0_refclk: pll0-refclk {
> clock@ ?
>> + clocks = <&k3_clks 297 9>, <&dummy_cmn_refclk>;
>> + clock-output-names = "wiz4_pll0_refclk";
>> + #clock-cells = <0>;
>> + assigned-clocks = <&wiz4_pll0_refclk>;
>> + assigned-clock-parents = <&k3_clks 297 9>;
>> + };
>> +
>> + wiz4_pll1_refclk: pll1-refclk {
> same?
>> + clocks = <&k3_clks 297 9>, <&dummy_cmn_refclk>;
>> + clock-output-names = "wiz4_pll1_refclk";
>> + #clock-cells = <0>;
>> + assigned-clocks = <&wiz4_pll1_refclk>;
>> + assigned-clock-parents = <&k3_clks 297 9>;
>> + };
>> +
>> + wiz4_refclk_dig: refclk-dig {
> same?
>> + clocks = <&k3_clks 297 9>, <&dummy_cmn_refclk>;
>> + clock-output-names = "wiz4_refclk_dig";
>> + #clock-cells = <0>;
>> + assigned-clocks = <&wiz4_refclk_dig>;
>> + assigned-clock-parents = <&k3_clks 297 9>;
>> + };
>> +
>> + wiz4_cmn_refclk_dig_div: cmn-refclk-dig-div {
> same?
>> + clocks = <&wiz4_refclk_dig>;
>> + #clock-cells = <0>;
>> + };
>> +
>> + wiz4_cmn_refclk1_dig_div: cmn-refclk1-dig-div {
> same?
>> + clocks = <&wiz4_pll1_refclk>;
>> + #clock-cells = <0>;
>> + };
>> +
>> + serdes4: serdes@5050000 {
>> + /*
>> + * Note: we also map DPTX PHY registers as the Torrent
>> + * needs to manage those.
>> + */
>> + compatible = "ti,j721e-serdes-10g";
>> + reg = <0x5050000 0x10000>,
>> + <0xa030a00 0x40>; /* DPTX PHY */
>> + reg-names = "torrent_phy", "dptx_phy";
>> +
>> + resets = <&serdes_wiz4 0>;
>> + reset-names = "torrent_reset";
>> + clocks = <&wiz4_pll0_refclk>;
>> + clock-names = "refclk";
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + torrent_phy_dp: phy@0 {
>> + reg = <0>;
>> + resets = <&serdes_wiz4 1>;
>> + cdns,phy-type = <PHY_TYPE_DP>;
>> + cdns,num-lanes = <4>;
>> + cdns,max-bit-rate = <5400>;
>> + #phy-cells = <0>;
>> + };
>> + };
>> + };
>> +
> Do you see any impact of the discussions we are having at [1] ?
You mean using wiz or serdes naming all around?
But I think the answer to all the comments is the same: I'm following what's already there for
serdes 0-3 in k3-j721e-main.dtsi, and what's defined in ti,phy-j721e-wiz.yaml.
Kishon is probably better person to answer about changes to the wiz naming.
Tomi
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-17 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 7:12 [PATCH 0/2] arm64: dts: ti: k3-j721e: Add DisplayPort Tomi Valkeinen
2020-09-17 7:12 ` [PATCH 1/2] arm64: dts: ti: k3-j721e-main: add DP & DP PHY Tomi Valkeinen
2020-09-17 13:07 ` Nishanth Menon
2020-09-17 13:52 ` Tomi Valkeinen [this message]
2020-09-17 7:12 ` [PATCH 2/2] arm64: dts: ti: k3-j721e-common-proc-board: add DP to j7 evm Tomi Valkeinen
[not found] <20220222163230.1566-1-r-ravikumar@ti.com>
[not found] ` <20220222163230.1566-2-r-ravikumar@ti.com>
2022-02-28 4:17 ` [PATCH 1/2] arm64: dts: ti: k3-j721e-main: add DP & DP PHY Kishon Vijay Abraham I
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=933cccf5-fa5c-dc46-36e5-3200e7b7801d@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=sjakhade@cadence.com \
--cc=t-kristo@ti.com \
--cc=yamonkar@cadence.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).