Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754294AbaF0WIg (ORCPT ); Fri, 27 Jun 2014 18:08:36 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:48284 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753297AbaF0WIe (ORCPT ); Fri, 27 Jun 2014 18:08:34 -0400 Message-ID: <53ADEB5F.5030502@wwwdotorg.org> Date: Fri, 27 Jun 2014 16:08:31 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Alexandre Courbot , Thierry Reding CC: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org, gnurou@gmail.com Subject: Re: [PATCH 0/2] ARM: tegra: roth: pinmux fixes References: <1403508779-25896-1-git-send-email-acourbot@nvidia.com> In-Reply-To: <1403508779-25896-1-git-send-email-acourbot@nvidia.com> X-Enigmail-Version: 1.5.2 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 On 06/23/2014 01:32 AM, Alexandre Courbot wrote: > Two small but important fixes to SHIELD's pinmux configuration. > The use of invalid properties caused the pinmux to not be applied > at all. Also the setting for sdmmc clock lines resulted in random > errors or even the impossibility to probe attached devices. > > Alexandre Courbot (2): > ARM: tegra: roth: fix unsupported pinmux properties > ARM: tegra: roth: enable input on mmc clock pins The series, applied to Tegra's for-3.17/dt branch. Sorry for the delay; I'd forgotten that our internal discussion resolved my questions about patch 2. Still looking forward to internal bugs files against the Jetson TK1 and Venice2 board pinmux spreadsheets for the same issue:-) -- 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/