Reviewed-by. Philip Rakity <prak...@nvidia.com> ----- Reply message ----- From: "Daniel Drake" <d...@laptop.org> To: "Philip Rakity" <prak...@nvidia.com> Cc: "c...@laptop.org" <c...@laptop.org>, "linux-...@vger.kernel.org" <linux-...@vger.kernel.org>, "jrudh...@gmail.com" <jrudh...@gmail.com>, "devicetree-discuss@lists.ozlabs.org" <devicetree-discuss@lists.ozlabs.org> Subject: [PATCH 1/2] sdhci: add quirk for lack of 1.8v support Date: Sun, Nov 25, 2012 18:50
On Sun, Nov 25, 2012 at 12:36 PM, Philip Rakity <prak...@nvidia.com> wrote: > The same effect can be achieved by setting the quirk > SDHCI_QUIRK_MISSING_CAPS > reading caps[0] and removing from caps[1] the UHS values in the controller > specific code for your board. > > What is the reason you cannot do this ? The same reasons we already touched upon in the other thread. http://marc.info/?l=linux-mmc&m=135240077826454&w=2 http://marc.info/?l=linux-mmc&m=135240181826846&w=2 To reiterate (I know this has been broken out over a couple of weeks): There is no controller-specific or board-specific code. We are working with the device tree. It must be done generically. SDHCI_QUIRK_MISSING_CAPS seems to be aimed at cases where the controller does not report caps, or it is lying about the caps it does/doesn't support. In this case our controller is being truthful, so this does not feel appropriate. Also, the only realistic way that I can see to combine SDHCI_QUIRK_MISSING_CAPS with the device tree would be to put the caps/caps1 override data in the device tree. This just seems ugly, and feels like it is taking the wrong approach of again suggesting that the controller is providing bad data, when in this case actually it is correctly saying that 1.8v is supported (by the controller - it obviously cannot speak for external components). We don't have a regulator to work with here. Thanks Daniel ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------
_______________________________________________ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss
