From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de ([212.227.17.8]:51301 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751193Ab3G2LK5 (ORCPT ); Mon, 29 Jul 2013 07:10:57 -0400 Date: Mon, 29 Jul 2013 13:10:52 +0200 (CEST) From: Guennadi Liakhovetski Subject: Re: [PATCH 1/2] mmc: add Device Tree properties for UHS modes In-Reply-To: <1375095436.3340.13.camel@hornet> Message-ID: References: <51F2ADA2.2030503@wwwdotorg.org> <1375095436.3340.13.camel@hornet> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: devicetree-owner@vger.kernel.org To: Pawel Moll Cc: Stephen Warren , "linux-sh@vger.kernel.org" , "linux-mmc@vger.kernel.org" , Magnus Damm , Chris Ball , "devicetree@vger.kernel.org" , Simon Horman , Ian Campbell , Mark Rutland , "rob.herring@calxeda.com" List-ID: On Mon, 29 Jul 2013, Pawel Moll wrote: > On Fri, 2013-07-26 at 18:10 +0100, Stephen Warren wrote: > > > +- uhs-sdr12: the host supports UHS SDR12 mode > > > +- uhs-sdr25: the host supports UHS SDR25 mode > > > +- uhs-sdr50: the host supports UHS SDR50 mode > > > +- uhs-sdr104: the host supports UHS SDR104 mode > > > +- uhs-ddr50: the host supports UHS DDR50 mode > > > +- ddr-1v2: the host can support DDR, using 1.2V VccQ > > > +- ddr-1v8: the host can support DDR, using 1.8V VccQ > > I understand that they are equivalent of the mmc caps #defines. Having > absolutely no UHS knowledge (nor access to the spec) I'm just wondering > if some of them couldn't be derived from the "environment", being the > way the host is wired up? Indeed it would be good to get a reply from someone with access to the specs. Thanks Guennadi > An example would be the classic OCR VDD fields - the voltage range bits > are taken from the regulator "vmmc" supply (see > mmc_regulator_get_supply()). > > Of course I this may be completely wrong approach here... > > Pawel --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer http://www.open-technology.de/