From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tero Kristo <t-kristo@ti.com>, Nishanth Menon <nm@ti.com>,
Rob Herring <robh+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Jyri Sarha <jsarha@ti.com>
Subject: Re: [PATCH 1/3] arm64: dts: ti: am654: Add DSS node
Date: Mon, 27 Apr 2020 13:50:23 +0300 [thread overview]
Message-ID: <3708a94a-9c42-745b-3dc0-2271fcc266a5@ti.com> (raw)
In-Reply-To: <591ddc8e-b45a-5a36-ae81-e1b92727dd2d@ti.com>
On 27/04/2020 13:08, Tero Kristo wrote:
> On 22/04/2020 12:15, Tomi Valkeinen wrote:
>> From: Jyri Sarha <jsarha@ti.com>
>>
>> Add DSS node to k3-am65-main.dtsi with labels for board specific
>> support and syscon node for oldi-io-ctrl.
>>
>> Signed-off-by: Jyri Sarha <jsarha@ti.com>
>> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
>> ---
>> arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 44 ++++++++++++++++++++++++
>> 1 file changed, 44 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
>> index 11887c72f23a..7d1bc991708e 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
>> @@ -287,6 +287,11 @@
>> mux-reg-masks = <0x4080 0x3>, /* SERDES0 lane select */
>> <0x4090 0x3>; /* SERDES1 lane select */
>> };
>> +
>> + dss_oldi_io_ctrl: dss_oldi_io_ctrl@41E0 {
>> + compatible = "syscon";
>> + reg = <0x0000041E0 0x14>;
>> + };
>> };
>> dwc3_0: dwc3@4000000 {
>> @@ -746,4 +751,43 @@
>> };
>> };
>> };
>> +
>> + dss: dss@04a00000 {
>> + compatible = "ti,am65x-dss";
>> + reg = <0x0 0x04a00000 0x0 0x1000>, /* common */
>> + <0x0 0x04a02000 0x0 0x1000>, /* vidl1 */
>> + <0x0 0x04a06000 0x0 0x1000>, /* vid */
>> + <0x0 0x04a07000 0x0 0x1000>, /* ovr1 */
>> + <0x0 0x04a08000 0x0 0x1000>, /* ovr2 */
>> + <0x0 0x04a0a000 0x0 0x1000>, /* vp1 */
>> + <0x0 0x04a0b000 0x0 0x1000>; /* vp2 */
>> + reg-names = "common", "vidl1", "vid",
>> + "ovr1", "ovr2", "vp1", "vp2";
>> +
>> + ti,am65x-oldi-io-ctrl = <&dss_oldi_io_ctrl>;
>> +
>> + power-domains = <&k3_pds 67 TI_SCI_PD_EXCLUSIVE>;
>> +
>> + clocks = <&k3_clks 67 1>,
>> + <&k3_clks 216 1>,
>> + <&k3_clks 67 2>;
>> + clock-names = "fck", "vp1", "vp2";
>> +
>> + /*
>> + * Set vp2 clk (DPI_1_IN_CLK) mux to PLL4 via
>> + * DIV1. See "Figure 12-3365. DSS Integration"
>> + * in AM65x TRM for details.
>> + */
>> + assigned-clocks = <&k3_clks 67 2>;
>> + assigned-clock-parents = <&k3_clks 67 5>;
>> +
>> + interrupts = <GIC_SPI 166 IRQ_TYPE_EDGE_RISING>;
>> +
>> + status = "disabled";
>
> Any reason why the node is disabled? Are you planning to enable it somewhere later on, or is that
> left for the user to do?
It's enabled in board DT files or DT overlays which add a display and the DT graph for the
connections. Having DSS driver probe without any displays is a waste of resources.
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
prev parent reply other threads:[~2020-04-27 10:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 9:15 [PATCH 1/3] arm64: dts: ti: am654: Add DSS node Tomi Valkeinen
2020-04-22 9:15 ` [PATCH 2/3] arm64: dts: ti: k3-j721e-main.dtsi: " Tomi Valkeinen
2020-04-27 10:09 ` Tero Kristo
2020-04-27 10:37 ` Jyri Sarha
2020-04-27 10:41 ` Tero Kristo
2020-04-27 10:49 ` Jyri Sarha
2020-04-27 10:51 ` Tomi Valkeinen
2020-04-27 11:10 ` Jyri Sarha
2020-04-27 11:15 ` Tomi Valkeinen
2020-04-27 11:37 ` Tomi Valkeinen
2020-04-27 11:41 ` Tero Kristo
2020-04-22 9:15 ` [PATCH 3/3] arm64: dts: ti: k3-j721e-common-proc-board: add assigned clks for DSS Tomi Valkeinen
2020-04-27 10:08 ` [PATCH 1/3] arm64: dts: ti: am654: Add DSS node Tero Kristo
2020-04-27 10:50 ` Tomi Valkeinen [this message]
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=3708a94a-9c42-745b-3dc0-2271fcc266a5@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jsarha@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.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