From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yang Kuankuan Subject: Re: [PATCH v2 06/12] drm: bridge/dw_hdmi: add audio support for more display resolutions Date: Sat, 31 Jan 2015 08:28:54 -0500 Message-ID: <54CCD896.4020603@rock-chips.com> References: <1422617031-25098-1-git-send-email-ykk@rock-chips.com> <1422617439-25564-1-git-send-email-ykk@rock-chips.com> <20150131112043.GY26493@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150131112043.GY26493@n2100.arm.linux.org.uk> Sender: linux-kernel-owner@vger.kernel.org To: Russell King - ARM Linux Cc: David Airlie , Philipp Zabel , Fabio Estevam , Shawn Guo , Rob Clark , Mark Yao , Daniel Vetter , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, djkurtz@chromium.org, dbehr@chromoum.org, mmind00@googlemail.com, dianders@chromium.org, marcheu@chromium.org, rockchip-discuss@chromium.org List-Id: dri-devel@lists.freedesktop.org On 01/31/2015 06:20 AM, Russell King - ARM Linux wrote: > On Fri, Jan 30, 2015 at 06:30:39AM -0500, Yakir Yang wrote: >> Add more n/cts values, in that case we can support audio for more >> display resolutions (128 * SampleRate = PixelClock * N / CTS). > Where do these come from? The iMX6 manuals give the set which are > already in the driver, and says that others are not supported - to > quote... > > "Table below shows the CTS and N values for the supported standard. > All other TMDS clocks are not supported, the TMDS clocks divided or > multiplied by 1,001 coefficients are not supported." > > and the table lists values for TMDS clocks of 25.2, 27, 54, 74.25, > 148.5 and 297MHz. > > This will need to be tested on iMX6 to validate whether it works. > If it doesn't work, we need to conditionalise the new TMDS clocks > with the IP version. > I just want to add audio support for some No-CEA display resolutions, and actually it can works on rk3288 platform. If it can not work on iMX6 platform, i will add IP verison select in next version v3. Thanks. : )