From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Doug Anderson <dianders@google.com>
Cc: Yuvaraj Kumar C D <yuvaraj.cd@samsung.com>,
Ulf Hansson <ulf.hansson@linaro.org>, "cpgs ." <cpgs@samsung.com>,
Yuvaraj Kumar C D <yuvaraj.cd@gmail.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
Chris Ball <cjb@laptop.org>,
Seung-Won Jeon <tgih.jun@samsung.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
Sonny Rao <sonnyrao@chromium.org>,
Tomasz Figa <tomasz.figa@gmail.com>,
Kukjin Kim <kgene.kim@samsung.com>,
SUNIL JOSHI <joshi@samsung.com>,
PRASHANTH GODREHAL <prashanth.g@samsung.com>,
ALIM AKHTAR <alim.akhtar@samsung.com>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Abhilash Kesavan <a.kesavan@samsung.com>
Subject: Re: [PATCH V2 1/3] mmc: dw_mmc: use mmc_regulator_get_supply to handle regulators
Date: Thu, 02 Oct 2014 18:06:51 +0200 [thread overview]
Message-ID: <1754745.SCGBco8pNI@amdc1032> (raw)
In-Reply-To: <CAD=FV=Xcv6E57u=kUj4QSWOpxCwOuJ4UyrFhSg1z0O1zx8nCag@mail.gmail.com>
Hi,
On Wednesday, October 01, 2014 09:04:09 AM Doug Anderson wrote:
> Hi,
>
> On Wed, Oct 1, 2014 at 7:00 AM, Bartlomiej Zolnierkiewicz
> <b.zolnierkie@samsung.com> wrote:
> >
> > Hi,
> >
> > On Wednesday, October 01, 2014 12:47:52 AM YUVARAJ CD wrote:
> >
> >> Since I am out of station, i dont have an access to my work set up.
> >> Can you send me the dts entries of sd crad and their corresponding regulator entries?
> >
> > From arch/arm/boot/dts/exynos5420-arndale-octa.dts:
> >
> > ...
> > mmc@12200000 {
> > status = "okay";
> > broken-cd;
> > supports-highspeed;
> > card-detect-delay = <200>;
> > samsung,dw-mshc-ciu-div = <3>;
> > samsung,dw-mshc-sdr-timing = <0 4>;
> > samsung,dw-mshc-ddr-timing = <0 2>;
> > pinctrl-names = "default";
> > pinctrl-0 = <&sd0_clk &sd0_cmd &sd0_bus4 &sd0_bus8>;
> > vmmc-supply = <&ldo10_reg>;
> >
> > slot@0 {
> > reg = <0>;
> > bus-width = <8>;
> > };
> > };
> >
> > mmc@12220000 {
> > status = "okay";
> > supports-highspeed;
> > card-detect-delay = <200>;
> > samsung,dw-mshc-ciu-div = <3>;
> > samsung,dw-mshc-sdr-timing = <2 3>;
> > samsung,dw-mshc-ddr-timing = <1 2>;
> > pinctrl-names = "default";
> > pinctrl-0 = <&sd2_clk &sd2_cmd &sd2_cd &sd2_bus4>;
> > vmmc-supply = <&ldo10_reg>;
> >
> > slot@0 {
> > reg = <0>;
> > bus-width = <4>;
> > };
> > };
> > ...
> > ldo10_reg: LDO10 {
> > regulator-name = "PVDD_PRE_1V8";
> > regulator-min-microvolt = <1800000>;
> > regulator-max-microvolt = <1800000>;
> > regulator-always-on;
> > };
>
> I don't have schematics for Arndale Octa, but the above is really
> fishy. "vmmc" shouldn't be 1.8V. That's the general power signal to
> MMC and should be 2.7V - 3.6V. "vqmmc" could be 1.8V in certain
> situations, but my understanding is that for maximum compatibility it
> should at least start out identical to "vmmc" (and later go down to
> 1.7V - 1.95V).
>
> My first thought would be to just remove the "vmmc-supply" from your
> DTS. I think we could land that and pick it back easily. That will
> get you something working and won't introduce any regressions because:
> 1. MMC core will give you a dummy regulator
> 2. The code will default to assuming that vmmc is 3.3V, which is what
> it used to do anyway.
> 3. The only referenced regulator is always on anyway.
>
> Separately you could specify a proper vmmc and maybe even a vqmmc.
>
> On SMDK5420 I see this for the SD card (mmc2):
> * vmmc should be "VDD_SD_2V8". From LDO19.
> * vqmmc should be "VDDQ_MMC2_AP". From LDO13.
>
> OK, I dug up the Arndale schematics. For mmc2:
> * vmmc should be PVDD_TFLASH_2V8. That's LDO19.
> * vqmmc (hooked up to VDDQ_MMC2): PVDD_APIO_MMCOFF_2V8. LDO13 just like SMDK.
>
> ...sadly it looks like Anrdale has a schematics problem that prevents
> you from doing UHS. I see that the data lines are pulled up to
> PVDD_TFLASH_2V8 (vmmc), not pulled up to PVDD_APIO_MMCOFF_2V8 (vqmmc).
> I think that means that if you ever lower vqmmc to 1.8V (as needed for
> UHS) then you'll still be pulling up to 2.8V. That's not good. You
> should probably make sure that both LDO13 and LDO19 are listed as
> being exactly 2.8V.
>
>
> Anyway, the above has (obviously) not been tested and is just based on
> a casual browsing of schematics. Please let me know how it goes.
Removing the "vmmc-supply" entry fixes the problem. Using LDO13 for vmmc
and LDO19 for vqmmc also works fine. I'll post a patch fixing the mmc2 DT
entry to Kukjin in a few minutes. Thank you for your help.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
WARNING: multiple messages have this Message-ID (diff)
From: b.zolnierkie@samsung.com (Bartlomiej Zolnierkiewicz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/3] mmc: dw_mmc: use mmc_regulator_get_supply to handle regulators
Date: Thu, 02 Oct 2014 18:06:51 +0200 [thread overview]
Message-ID: <1754745.SCGBco8pNI@amdc1032> (raw)
In-Reply-To: <CAD=FV=Xcv6E57u=kUj4QSWOpxCwOuJ4UyrFhSg1z0O1zx8nCag@mail.gmail.com>
Hi,
On Wednesday, October 01, 2014 09:04:09 AM Doug Anderson wrote:
> Hi,
>
> On Wed, Oct 1, 2014 at 7:00 AM, Bartlomiej Zolnierkiewicz
> <b.zolnierkie@samsung.com> wrote:
> >
> > Hi,
> >
> > On Wednesday, October 01, 2014 12:47:52 AM YUVARAJ CD wrote:
> >
> >> Since I am out of station, i dont have an access to my work set up.
> >> Can you send me the dts entries of sd crad and their corresponding regulator entries?
> >
> > From arch/arm/boot/dts/exynos5420-arndale-octa.dts:
> >
> > ...
> > mmc at 12200000 {
> > status = "okay";
> > broken-cd;
> > supports-highspeed;
> > card-detect-delay = <200>;
> > samsung,dw-mshc-ciu-div = <3>;
> > samsung,dw-mshc-sdr-timing = <0 4>;
> > samsung,dw-mshc-ddr-timing = <0 2>;
> > pinctrl-names = "default";
> > pinctrl-0 = <&sd0_clk &sd0_cmd &sd0_bus4 &sd0_bus8>;
> > vmmc-supply = <&ldo10_reg>;
> >
> > slot at 0 {
> > reg = <0>;
> > bus-width = <8>;
> > };
> > };
> >
> > mmc at 12220000 {
> > status = "okay";
> > supports-highspeed;
> > card-detect-delay = <200>;
> > samsung,dw-mshc-ciu-div = <3>;
> > samsung,dw-mshc-sdr-timing = <2 3>;
> > samsung,dw-mshc-ddr-timing = <1 2>;
> > pinctrl-names = "default";
> > pinctrl-0 = <&sd2_clk &sd2_cmd &sd2_cd &sd2_bus4>;
> > vmmc-supply = <&ldo10_reg>;
> >
> > slot at 0 {
> > reg = <0>;
> > bus-width = <4>;
> > };
> > };
> > ...
> > ldo10_reg: LDO10 {
> > regulator-name = "PVDD_PRE_1V8";
> > regulator-min-microvolt = <1800000>;
> > regulator-max-microvolt = <1800000>;
> > regulator-always-on;
> > };
>
> I don't have schematics for Arndale Octa, but the above is really
> fishy. "vmmc" shouldn't be 1.8V. That's the general power signal to
> MMC and should be 2.7V - 3.6V. "vqmmc" could be 1.8V in certain
> situations, but my understanding is that for maximum compatibility it
> should at least start out identical to "vmmc" (and later go down to
> 1.7V - 1.95V).
>
> My first thought would be to just remove the "vmmc-supply" from your
> DTS. I think we could land that and pick it back easily. That will
> get you something working and won't introduce any regressions because:
> 1. MMC core will give you a dummy regulator
> 2. The code will default to assuming that vmmc is 3.3V, which is what
> it used to do anyway.
> 3. The only referenced regulator is always on anyway.
>
> Separately you could specify a proper vmmc and maybe even a vqmmc.
>
> On SMDK5420 I see this for the SD card (mmc2):
> * vmmc should be "VDD_SD_2V8". From LDO19.
> * vqmmc should be "VDDQ_MMC2_AP". From LDO13.
>
> OK, I dug up the Arndale schematics. For mmc2:
> * vmmc should be PVDD_TFLASH_2V8. That's LDO19.
> * vqmmc (hooked up to VDDQ_MMC2): PVDD_APIO_MMCOFF_2V8. LDO13 just like SMDK.
>
> ...sadly it looks like Anrdale has a schematics problem that prevents
> you from doing UHS. I see that the data lines are pulled up to
> PVDD_TFLASH_2V8 (vmmc), not pulled up to PVDD_APIO_MMCOFF_2V8 (vqmmc).
> I think that means that if you ever lower vqmmc to 1.8V (as needed for
> UHS) then you'll still be pulling up to 2.8V. That's not good. You
> should probably make sure that both LDO13 and LDO19 are listed as
> being exactly 2.8V.
>
>
> Anyway, the above has (obviously) not been tested and is just based on
> a casual browsing of schematics. Please let me know how it goes.
Removing the "vmmc-supply" entry fixes the problem. Using LDO13 for vmmc
and LDO19 for vqmmc also works fine. I'll post a patch fixing the mmc2 DT
entry to Kukjin in a few minutes. Thank you for your help.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2014-10-02 16:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01.09.14890.83F4B245@epcpsbge5.samsung.com>
2014-10-01 14:00 ` [PATCH V2 1/3] mmc: dw_mmc: use mmc_regulator_get_supply to handle regulators Bartlomiej Zolnierkiewicz
2014-10-01 14:00 ` Bartlomiej Zolnierkiewicz
2014-10-01 16:04 ` Doug Anderson
2014-10-01 16:04 ` Doug Anderson
2014-10-02 16:06 ` Bartlomiej Zolnierkiewicz [this message]
2014-10-02 16:06 ` Bartlomiej Zolnierkiewicz
2014-08-22 13:47 [PATCH V2 0/3] Adding UHS support for dw_mmc driver Yuvaraj Kumar C D
2014-08-22 13:47 ` [PATCH V2 1/3] mmc: dw_mmc: use mmc_regulator_get_supply to handle regulators Yuvaraj Kumar C D
2014-08-22 13:47 ` Yuvaraj Kumar C D
2014-08-25 12:32 ` Jaehoon Chung
2014-08-25 12:32 ` Jaehoon Chung
2014-08-25 15:06 ` Doug Anderson
2014-08-25 15:06 ` Doug Anderson
2014-08-29 11:34 ` Ulf Hansson
2014-08-29 11:34 ` Ulf Hansson
2014-09-29 12:31 ` Bartlomiej Zolnierkiewicz
2014-09-29 12:31 ` Bartlomiej Zolnierkiewicz
2014-09-30 5:23 ` Jaehoon Chung
2014-09-30 5:23 ` Jaehoon Chung
2014-10-01 13:57 ` Bartlomiej Zolnierkiewicz
2014-10-01 13:57 ` Bartlomiej Zolnierkiewicz
2014-10-01 14:14 ` Bartlomiej Zolnierkiewicz
2014-10-01 14:14 ` Bartlomiej Zolnierkiewicz
2014-09-30 17:22 ` Doug Anderson
2014-09-30 17:22 ` Doug Anderson
2014-10-01 13:06 ` Bartlomiej Zolnierkiewicz
2014-10-01 13:06 ` Bartlomiej Zolnierkiewicz
2014-10-01 15:38 ` Doug Anderson
2014-10-01 15:38 ` Doug Anderson
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=1754745.SCGBco8pNI@amdc1032 \
--to=b.zolnierkie@samsung.com \
--cc=a.kesavan@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=cjb@laptop.org \
--cc=cpgs@samsung.com \
--cc=dianders@google.com \
--cc=javier.martinez@collabora.co.uk \
--cc=jh80.chung@samsung.com \
--cc=joshi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=prashanth.g@samsung.com \
--cc=sonnyrao@chromium.org \
--cc=tgih.jun@samsung.com \
--cc=tomasz.figa@gmail.com \
--cc=ulf.hansson@linaro.org \
--cc=yuvaraj.cd@gmail.com \
--cc=yuvaraj.cd@samsung.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.