Received: by 10.223.185.116 with SMTP id b49csp1042579wrg; Wed, 21 Feb 2018 11:04:53 -0800 (PST) X-Google-Smtp-Source: AH8x227n1H/zOX5YiejZRffBUthOeWKDmlGWYoQPJUO1d2YYREV3hs4s5rX3ZRBvru8kzwHkxY9/ X-Received: by 2002:a17:902:8285:: with SMTP id y5-v6mr4119224pln.190.1519239893023; Wed, 21 Feb 2018 11:04:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519239892; cv=none; d=google.com; s=arc-20160816; b=ss8vOL8bbe7OqZVjuSvNMfrL9ng//SIKYuQYzQLiIvlFnnBhbgWROWiLteGWd8/PLu 7FJ2qgOD43+lh7K8B12efsOMBVmOZ9Iu+VWDNjDN8aGGwkra4Svcfs92fJJX6Cmwxy41 PUaCzjvAQrSp1zR2ngDawB6lCyzBJltwPG8UI5rhwf7kpjeEcw/adc1Ez3xn5L8PM7Gy ztH5nSHJu3TbVfm+6TT59MEvKftdv/zQ4yD7AZXTUv2F/0iFnMmkDbM8X4pIYN1NrxKj qg+3Qvsn5aeJyPYiDHZNVlZO7XZmaClB28cru0B1qiMYntdwchGpYbK21bwBqXlJN42K iyLA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=YFqy6FzyTwoeT1RWfaZ/VlHv9HjvSdK5s++r8MnI81Q=; b=fvziShYfhw5dfviIdcIJhP2cpefVArC4BQGiZiK/uDarqr9R+ko6qHukRKpvWqf3y4 3HMjwG4/sQYkzorYaR9ZiKqOu7fEqdpHw8C1DXtDP748viJajNR00/4cGex5OGXBlT8v +ThcO71BDB3FM1H9/bA381HEQPdPz34NaNilH9B6f3LQy4mNBcmUI0hqBiH9N1CReXuA ooMUgp1SSMV6qxHhtCxXXgCmG2DM2ro8cvuXd/iezYRnTCi3FgmZvXfWWuMgWMz2wibD tZk0/qQeh0Pa/uX0db7BA8YmlbcSvSN1QNOici04LZQEncaRDAVQAHXKWtW0SD4hnyqx IP4g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p184si3751658pga.700.2018.02.21.11.04.38; Wed, 21 Feb 2018 11:04:52 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S937458AbeBUQqe (ORCPT + 99 others); Wed, 21 Feb 2018 11:46:34 -0500 Received: from avon.wwwdotorg.org ([104.237.132.123]:38712 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933280AbeBUQqb (ORCPT ); Wed, 21 Feb 2018 11:46:31 -0500 Received: from [10.20.204.51] (thunderhill.nvidia.com [216.228.112.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by avon.wwwdotorg.org (Postfix) with ESMTPSA id EB2CA1C05E7; Wed, 21 Feb 2018 09:46:29 -0700 (MST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.99.2 at avon.wwwdotorg.org Subject: Re: [PATCH] ARM: dtc: tegra: enable front panel leds in TrimSlice To: Tomasz Maciej Nowak Cc: thierry.reding@gmail.com, jonathanh@nvidia.com, linux-tegra@vger.kernel.org, robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org References: <20180219201623.6987-1-tmn505@gmail.com> <57945bd2-d8c2-f7bc-f01f-29d679762446@wwwdotorg.org> <873b01dc-3ca5-3151-2654-a8272cb9dd88@gmail.com> From: Stephen Warren Message-ID: Date: Wed, 21 Feb 2018 09:46:28 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <873b01dc-3ca5-3151-2654-a8272cb9dd88@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/21/2018 09:20 AM, Tomasz Maciej Nowak wrote: > W dniu 20.02.2018 o 20:55, Stephen Warren pisze: >> On 02/19/2018 01:16 PM, Tomasz Maciej Nowak wrote: >>> Adds device nodes for two front panel LEDs. >> >> Why do you need to change the pinmux settings? Configuring a pin as a >> GPIO should override any pinmux special function selection and hence >> make it irrelevant, so I don't think you should need to change the >> pinmux. > > At first I did exactly that without changing the pinmux, but the LEDs > didn't light up. After that I compared with CompuLab source tree [1]. > The pinmux was specified as in my patch. With this change the LEDs are > fully functional. > > 1. > https://gitorious.org/trimslice-kernel/trimslice-kernel?p=trimslice-kernel:trimslice-kernel.git;a=blob;f=arch/arm/mach-tegra/board-trimslice-pinmux.c;h=cc6d5225d97eb9327c820bf1d5b2bc16ab8c6dda;hb=d25bf45d6314089489b30d218ed8a0d6d94417f9#l45 Oh I see. Your patch isn't changing the pinmux function selection but the other configuration bits, which are relevant even when the pin is in GPIO mode. In particular, it clears the tristate bit for the dte pingroup. That makes perfect sense.