| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 20 Nov 2012 09:42:50 +0100 From: Marek Szyprowski <m.szyprowski@...sung.com> To: Philip Rakity <prakity@...dia.com> Cc: "linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>, "linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>, Kyungmin Park <kyungmin.park@...sung.com>, Mark Brown <broonie@...nsource.wolfsonmicro.com>, Liam Girdwood <lrg@...com>, Chris Ball <cjb@...top.org> Subject: Re: [PATCH v2] mmc: sdhci: apply voltage range check only for non-fixed regulators On 11/13/2012 10:23 PM, Philip Rakity wrote: > Hi Marek, > > Is the regulator dedicated ? or is it shared ? Is it used for eMMC ? > > If it cannot be turned off -- then just don't list it in the regulators list for vmmc. > > If it CAN be turned off then need to get back to you. It is dedicated to eMMC device and can be turned off. Patch "mmc: sdhci: apply voltage range check only for non-fixed regulators" restored sdhci to working state after merging the regulator fix. However there are lots of error messages from sdhci driver: s3c-sdhci s3c-sdhci.0: could not set regulator OCR (-1) The only remaining problem is sdhci driver operation with dummy regulator. Right now it simply fails to initialize if dummy regulator is enabled. Do you have any idea how to fix it properly? Best regards -- Marek Szyprowski Samsung Poland R&D Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists