From: Ludovic Desroches <ludovic.desroches@atmel.com>
To: <ulf.hansson@linaro.org>, <nicolas.ferre@atmel.com>,
<alexandre.belloni@free-electrons.com>
Cc: <linux-mmc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<plagnioj@jcrosoft.com>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <pierre.samat@atmel.com>,
Ludovic Desroches <ludovic.desroches@atmel.com>
Subject: [PATCH 0/2] mmc: sdhci: potentially bad behavior when using vmmc supply
Date: Fri, 6 Nov 2015 16:59:28 +0100 [thread overview]
Message-ID: <1446825570-30029-1-git-send-email-ludovic.desroches@atmel.com> (raw)
Hi,
I would like to have some feedback for these two patches. I have two questions.
1.
To suppress the warnings telling me I have no vmmc and vqmmc supplies, I have
added them and discovered that adding a vmmc supply involve only writing 1 in
the Power Control Register involves enabling the SD Bus Power with a non valid
value for the SD Bus Voltage. If the host controllers strictly follows the
specification, it shall not enable SD Bus Power. So enough if it seems useless
to configure SD Bus Voltage because we have an external regulator, do it.
By the way, I am curious to understand what is really the SD Bus Voltage. I
mean talking about bus voltage makes me thinking more about vqmmc than vmmc.
Is it only bad naming or do I miss something?
>From the specification, there is this figure:
HOST
---------------------------------------------------
| ------------ 3.3V | VDD
| | Power SW |------------------------------------|----------
| ------------ | | |
| ---------| | |
| | | |
| -------------- ---------------------- |
| | Ref. Volt. |-----| Regulator/Selector | |
| -------------- ---------------------- |
| 3.3V/1.8V | |
| | |
| |--------------- |
| | | | | |
| | R R _ |
| | | | _ |
| | | | | |
| | | | /// |
| ------- | | | CLK
| | |----)--)------|----------
| ----------------------- |Multi| | | | CMD
| |Random Logic Circuits|---|Drive|----)---------|----------
| ----------------------- |I/O | | | DAT
| | |--------------|----------
| ------- |
---------------------------------------------------
In my mind vmmc is the 3.3V signal and vqmmc is the 3.3V/1.8V signal, so why
talking about bus voltage?
2.
Is the regulator-gpio usage the right thing to do for vqmmc? In my case it is
not really driven by a gpio but by a pio from the sdhci device. In the binding,
declaring the gpio is an option so I thought using this regulator fits my need.
P.S. patch 2 is based on another patch not yet in next:
http://www.spinics.net/lists/arm-kernel/msg453447.html
Thanks
Ludovic
Ludovic Desroches (2):
mmc: sdhci: set bus voltage before enabling bus power
ARM: at91/dt: sama5d2 Xplained: add regulators for sdhci devices
arch/arm/boot/dts/at91-sama5d2_xplained.dts | 14 ++++++++++++++
drivers/mmc/host/sdhci.c | 7 -------
2 files changed, 14 insertions(+), 7 deletions(-)
--
2.5.0
next reply other threads:[~2015-11-06 15:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 15:59 Ludovic Desroches [this message]
2015-11-06 15:59 ` [PATCH 1/2] mmc: sdhci: set bus voltage before enabling bus power Ludovic Desroches
2015-11-09 13:23 ` Ludovic Desroches
2015-11-09 14:12 ` Ulf Hansson
2015-11-09 14:40 ` Ludovic Desroches
2015-11-09 16:00 ` Ulf Hansson
2015-11-09 16:30 ` Ludovic Desroches
2015-11-24 9:23 ` Ludovic Desroches
2015-11-24 11:01 ` Ulf Hansson
2015-11-24 13:12 ` Ludovic Desroches
2015-11-24 13:56 ` Ulf Hansson
2015-11-24 14:08 ` Ludovic Desroches
2015-11-24 15:17 ` Ulf Hansson
2015-11-06 15:59 ` [PATCH 2/2] ARM: at91/dt: sama5d2 Xplained: add regulators for sdhci devices Ludovic Desroches
2015-11-06 16:42 ` [PATCH 0/2] mmc: sdhci: potentially bad behavior when using vmmc supply Ulf Hansson
2015-11-09 7:41 ` Ludovic Desroches
2015-11-09 9:38 ` Ulf Hansson
2015-11-09 10:25 ` Ludovic Desroches
2015-11-09 10:50 ` Ulf Hansson
2015-11-09 13:14 ` Ludovic Desroches
2015-11-09 13:18 ` Ulf Hansson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1446825570-30029-1-git-send-email-ludovic.desroches@atmel.com \
--to=ludovic.desroches@atmel.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=pierre.samat@atmel.com \
--cc=plagnioj@jcrosoft.com \
--cc=ulf.hansson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®