From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH RFC 1/3] DT: bindings: mmc: Add property for 3.3V only support Date: Wed, 10 Aug 2016 13:44:51 -0500 Message-ID: <20160810184451.GA13473@rob-hp-laptop> References: <1470488140-10104-1-git-send-email-stefan.wahren@i2se.com> <1470488140-10104-2-git-send-email-stefan.wahren@i2se.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1470488140-10104-2-git-send-email-stefan.wahren@i2se.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Stefan Wahren Cc: Mark Rutland , Dong Aisheng , Ulf Hansson , Marek Vasut , Otavio Salvador , devicetree@vger.kernel.org, Shawn Guo , linux-mmc@vger.kernel.org, Sascha Hauer , Fabio Estevam , Holger Schurig , linux-arm-kernel@lists.infradead.org List-Id: linux-mmc@vger.kernel.org On Sat, Aug 06, 2016 at 12:55:38PM +0000, Stefan Wahren wrote: > Currently there is no proper way to define that a MMC host supports > only 3.3V. The property no-1-8-v is broken and has different meanings > for different sdhci variants. So add a new property for 3.3V only > support and mark no-1-8-v as deprecated. Why is it broken? How would I override a controller saying 1.8V is supported and it is not? Rob