Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752212AbaLCNKm (ORCPT ); Wed, 3 Dec 2014 08:10:42 -0500 Received: from metis.ext.pengutronix.de ([92.198.50.35]:56335 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752000AbaLCNKk (ORCPT ); Wed, 3 Dec 2014 08:10:40 -0500 Message-ID: <1417612197.5124.12.camel@pengutronix.de> Subject: Re: [PATCH v15 12/12] drm: bridge/dw_hdmi: add rockchip rk3288 support From: Philipp Zabel To: Andy Yan Cc: airlied@linux.ie, heiko@sntech.de, fabio.estevam@freescale.com, rmk+kernel@arm.linux.org.uk, Greg Kroah-Hartman , Grant Likely , Rob Herring , Shawn Guo , Josh Boyer , Sean Paul , Inki Dae , Dave Airlie , Arnd Bergmann , Lucas Stach , Zubair.Kakakhel@imgtec.com, djkurtz@google.com, ykk@rock-chips.com, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, devel@driverdev.osuosl.org, devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org, jay.xu@rock-chips.com, Pawel Moll , mark.yao@rock-chips.com, Mark Rutland , vladimir_zapolskiy@mentor.com, Ian Campbell , Kumar Gala Date: Wed, 03 Dec 2014 14:09:57 +0100 In-Reply-To: <547F02CF.9010804@rock-chips.com> References: <1417505778-18341-1-git-send-email-andy.yan@rock-chips.com> <1417506327-18908-1-git-send-email-andy.yan@rock-chips.com> <1417515882.3411.8.camel@pengutronix.de> <547DB1ED.7000409@rock-chips.com> <1417525257.3411.12.camel@pengutronix.de> <547F02CF.9010804@rock-chips.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.7-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:67c:670:100:96de:80ff:fec2:9969 X-SA-Exim-Mail-From: p.zabel@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Andy, Am Mittwoch, den 03.12.2014, 20:32 +0800 schrieb Andy Yan: > > My question is not about the available gates at the SoC level, but about > > the actual clock inputs from point of view of the HDMI TX IP. > > > > It could be that the hdmi_ctrl_clk gates all inputs to the module and > > bus clocks together. If so, you could just reuse "isfr" and "iahb" and > > set it to the same clock. If not, we'd need to think of something else. > > Unfortunately I don't have any Synopsys documentation of the HDMI TX at > > that level. > > After confirming with the IC designer, we finally make clear that > Rockchip RK3288 almost use the same clock design with imx: > clk-----iahbclk, used for hdmi module and bus > hdcp_clk-----isfrclk, used for hdcp and i2cm > cecclk -----cecclk, but this clk can be gated on rockchip, this is > different with imx, > but we don't handle the cec stuff now. So i will try to reuse the > imx clk binds. do you > think that is ok? Thank you for taking the time to verify this. So we should move the clock handling out of the soc specific parts into the common driver and reuse the existing clock bindings ("iahb", "isfr"). I'd suggest to add the "cec" clock now to the binding document as an optional clock, then you can already specify it in the rockchip dtsi. regards Philipp -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/