From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH] omap3: Fix 3630 mux errors Date: Thu, 29 Apr 2010 14:10:20 -0700 Message-ID: <20100429211020.GA29604@atomide.com> References: <1272526065-29683-1-git-send-email-manjugk@ti.com> <20100429182512.GN7225@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-01-ewr.mailhop.org ([204.13.248.71]:51818 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758411Ab0D3RGN (ORCPT ); Fri, 30 Apr 2010 13:06:13 -0400 Content-Disposition: inline In-Reply-To: <20100429182512.GN7225@atomide.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Manjunatha GK Cc: linux-omap@vger.kernel.org, Allen Pais , Paul Walmsley * Tony Lindgren [100429 11:20]: > * Manjunatha GK [100429 00:23]: > > From: Allen Pais > > > > The omap3630 has more mux signals than 34xx. The additional > > pins exist in omap36xx_cbp_subset, but are not initialized > > as the superset is missing these offsets. This causes the > > following errors during the boot: > > I have an earlier version of this queued up, will take a look > and see if they're the same: > > https://patchwork.kernel.org/patch/87555/ Turns out these are all non-muxable pins. So the right fix is to remove them from the 3630 ball table. Will post a patch shortly for this along with my other fixes. Regards, Tony