Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759841Ab2JYPh1 (ORCPT ); Thu, 25 Oct 2012 11:37:27 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:39983 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758614Ab2JYPh0 (ORCPT ); Thu, 25 Oct 2012 11:37:26 -0400 Message-ID: <50895CB2.8040103@wwwdotorg.org> Date: Thu, 25 Oct 2012 09:37:22 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: Mark Zhang CC: "linux@arm.linux.org.uk" , "linux-tegra@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] ARM: dt: tegra: ventana: define pinmux for ddc References: <1350626311-18131-1-git-send-email-markz@nvidia.com> <50817668.6020709@wwwdotorg.org> <5084F5D1.7050005@nvidia.com> <50857EEF.2070707@wwwdotorg.org> <5088DCF2.7030000@nvidia.com> In-Reply-To: <5088DCF2.7030000@nvidia.com> X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1520 Lines: 29 On 10/25/2012 12:32 AM, Mark Zhang wrote: > On 10/23/2012 01:14 AM, Stephen Warren wrote: ... >> I don't recall why pta was defined to be HDMI. The issue isn't that this >> patch changes the pinmux selection for the pta pingroup, but simply that >> both the pinctrl node's state definition, and the new I2C mux node's >> state definition both attempt to configure pingroup pta. The solution is >> most likely to simply remove the pta configuration from the main pinctrl >> node. > > Understood. I tried to remove the hdmi function definition of pta > pingroup yesterday then found HDMI can't work anymore. The EDID of HDMI > monitor can't be fetched. After some debugging, I have found that it's > caused by "i2c-mux-pinctrl" driver is loaded after drm driver. That > makes drm driver can't get EDID data via this i2c mux adapter because it > doesn't exist at that time. So I think we need to promote the load level > of "i2c-mux-pinctrl" driver. Any other ideas? (BTW, your message that I'm replying to wasn't word-wrapped correctly) No, i2c-mux-pinctrl shouldn't need to change. It sounds like tegra-drm isn't supporting deferred probe correctly; when it needs access to an I2C adapter that doesn't exist, it should defer its own probe until the I2C adapter does exist. -- 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/