Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932304AbbLBBWJ (ORCPT ); Tue, 1 Dec 2015 20:22:09 -0500 Received: from muru.com ([72.249.23.125]:49989 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752893AbbLBBWH (ORCPT ); Tue, 1 Dec 2015 20:22:07 -0500 Date: Tue, 1 Dec 2015 17:22:01 -0800 From: Tony Lindgren To: Matthijs van Duin Cc: lkml , "linux-omap@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Brian Hutchinson , Delio Brignoli , Neil Armstrong , Philipp Rosenberger Subject: Re: [PATCH 10/10] ARM: dts: Fix dm814x pinctrl address and mask Message-ID: <20151202012200.GZ23396@atomide.com> References: <1449013103-23238-1-git-send-email-tony@atomide.com> <1449013103-23238-11-git-send-email-tony@atomide.com> <20151202004623.GX23396@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1059 Lines: 26 * Matthijs van Duin [151201 17:15]: > On 2 December 2015 at 01:46, Tony Lindgren wrote: > > Ouch. We should probably have separate PIN_INPUT_3V3 and PIN_OUTPUT_3V3 > > dts macros that ensure that? > > Can't we just keep bit 18 out of the function mask? The bootloader > should already have made sure all pins have bit 18 set (and bit 19 set > to correct values after ROM mucked them up, see advisory 2.1.88), so > all that needs to be done is avoid touching them. Sounds good to me. And people who really want to override the mask can do it in the board specifc dts file. > Are the power savings from disabling unnecessary inputs significant > enough to spend any headache on it? Only for some battery powered devices, not in this case for sure. Regards,. Tony -- 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/