[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <427dc37e-1bf5-d3d7-f4af-1a0ee980f28b@ti.com>
Date: Mon, 25 Sep 2023 12:16:10 +0530
From: Jayesh Choudhary <j-choudhary@...com>
To: Maxime Ripard <mripard@...nel.org>,
Tomi Valkeinen <tomi.valkeinen@...asonboard.com>,
<r-ravikumar@...com>
CC: <nm@...com>, <vigneshr@...com>, <afd@...com>, <rogerq@...nel.org>,
<s-vadapalli@...com>, <kristo@...nel.org>, <robh+dt@...nel.org>,
<krzysztof.kozlowski+dt@...aro.org>, <conor+dt@...nel.org>,
<a-bhatia1@...com>, <sabiya.d@...com>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v9 3/5] arm64: dts: ti: k3-j784s4-main: Add DSS and
DP-bridge node
Hello Maxime,
On 17/08/23 16:24, Maxime Ripard wrote:
> Hi,
>
> On Thu, Aug 03, 2023 at 01:34:39PM +0530, Jayesh Choudhary wrote:
>> From: Rahul T R <r-ravikumar@...com>
>>
>> Add DSS and DP-bridge node for J784S4 SoC. DSS IP in J784S4 is
>> same as DSS IP in J721E, so same compatible is being used.
>> The DP is Cadence MHDP8546.
>>
[...]
>> +
>> + dss: dss@...0000 {
>> + compatible = "ti,j721e-dss";
>
> As far as I can see, this compatible limits the (DPI) pixel clock to
> 160MHz, but the TRM seems to mention that it's 600MHz?
>
> Is it expected?
>
I am unsure about why the max DPI pixel clock was set to 170MHz for
videoport bus type DISPC_VP_DPI.
Bus type DISPC_VP_DPI is used only for tfp410 bridge which can support
min 6.06ns pixel period (165MHz pixel clk).
I think the max value however should still be independent to what the
bridge can support.
We can look into this issue independent to this series.
Tomi,
Any comments here..
There should not be any issue making the max pixel clock for DPI bus
type 600 MHz as well????
-Jayesh
Powered by blists - more mailing lists