From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756285Ab3LFGX7 (ORCPT ); Fri, 6 Dec 2013 01:23:59 -0500 Received: from hqemgate15.nvidia.com ([216.228.121.64]:13382 "EHLO hqemgate15.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751338Ab3LFGXz (ORCPT ); Fri, 6 Dec 2013 01:23:55 -0500 X-PGP-Universal: processed; by hqnvupgp08.nvidia.com on Thu, 05 Dec 2013 22:17:11 -0800 Message-ID: <52A16CCE.7030304@nvidia.com> Date: Fri, 6 Dec 2013 11:51:02 +0530 From: Laxman Dewangan User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2 MIME-Version: 1.0 To: Stephen Warren CC: "linus.walleij@linaro.org" , "rob.herring@calxeda.com" , "pawel.moll@arm.com" , "mark.rutland@arm.com" , "ijc+devicetree@hellion.org.uk" , "thierry.reding@gmail.com" , "grant.likely@linaro.org" , "devicetree@vger.kernel.org" , "linux-doc@vger.kernel.org" , "linux-tegra@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH 1/4] pinctrl: tegra: Add devicetree binding document for Tegra124 References: <1386241070-4350-1-git-send-email-ldewangan@nvidia.com> <1386241070-4350-2-git-send-email-ldewangan@nvidia.com> <52A10973.5000101@wwwdotorg.org> In-Reply-To: <52A10973.5000101@wwwdotorg.org> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday 06 December 2013 04:47 AM, Stephen Warren wrote: > On 12/05/2013 03:57 AM, Laxman Dewangan wrote: >> This device tree binding document describes the Tegra124 pincontrol >> DT bindings. This document lists all valid properties, names, mux >> options of Tegra124 pins. > Is this a repost of what Ashwini sent a few weeks back, or V2? If V2, > it'd be useful to know what changed... I am not aware that Ashwini already sent back. I did not get chance to talk to her on this. I was thinking that it is still in internal review. Anyhow, I compare the downstream to your linux-next-common and found some diff. Something fixed in your tree which need downstream and something fixed in downstream which need to upstream. :) One diff is Mux enums are: TEGRA_MUX_SATA, TEGRA_MUX_CCLA, TEGRA_MUX_PE0, TEGRA_MUX_PE, TEGRA_MUX_PE1, TEGRA_MUX_DP, TEGRA_MUX_RTCK, TEGRA_MUX_SYS, TEGRA_MUX_CLK, TEGRA_MUX_TMDS, }; Functions definitions are: FUNCTION(sata), FUNCTION(ccla), FUNCTION(rtck), FUNCTION(pe0), FUNCTION(pe), FUNCTION(pe1), FUNCTION(dp), I think I will post the patch to fix this issue.