All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Anderson <dianders@chromium.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "addy ke" <addy.ke@rock-chips.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Pawel Moll" <pawel.moll@arm.com>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
	"Kumar Gala" <galak@codeaurora.org>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"tgih.jun@samsung.com" <tgih.jun@samsung.com>,
	"Jaehoon Chung" <jh80.chung@samsung.com>,
	"Chris Ball" <chris@printf.net>,
	"Dinh Nguyen" <dinguyen@altera.com>,
	"Heiko Stübner" <heiko@sntech.de>,
	"Olof Johansson" <olof@lixom.net>,
	"Sonny Rao" <sonnyrao@chromium.org>,
	"Alexandru Stan" <amstan@chromium.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	"zhenfu.fang" <zhenfu.fang@rock-chips.com>,
	"Eddie Cai" <cf@rock-chips.com>, lintao <lintao@rock-chips.com>,
	chenfen <chenfen@rock-chips.com>, zyf <zyf@rock-chips.com>,
	"Jianqun Xu" <xjq@rock-chips.com>,
	"Tao Huang" <huangtao@rock-chips.com>,
	"Chris Zhong" <zyw@rock-chips.com>, 姚智情 <yzq@rock-chips.com>,
	"han jiang" <hj@rock-chips.com>,
	"Kever Yang" <kever.yang@rock-chips.com>,
	zhangqing <zhangqing@rock-chips.com>,
	"Lin Huang" <hl@rock-chips.com>
Subject: Re: [PATCH] mmc: dw_mmc: try pick the exact same voltage as vmmc for vqmmc
Date: Fri, 21 Nov 2014 09:42:08 -0800	[thread overview]
Message-ID: <CAD=FV=Ve1TY4+8quq1=18A1YOFvOWuFGrBmHLwMCwdWBSqzxOw@mail.gmail.com> (raw)
In-Reply-To: <CAPDyKFrzGfDew0eLLEcA+_iS_mo-O2bFU58fjirfXXA8AJ9UYQ@mail.gmail.com>

Ulf,

On Fri, Nov 21, 2014 at 4:06 AM, Ulf Hansson <ulf.hansson@linaro.org> wrote:
> [...]
>
>> Sure
>> If the first card is sd2.0 since startup, dw_mci_switch_voltage will not be called,
>
> That can't be right. mmc_power_up() should trigger
> dw_mci_switch_voltage() to be invoked.

Hmmm, I think you're right.  Addy: can you double check if it's only
the 2nd card for you?  I was thinking that if a regulator is currently
3.3V and you request 2.7 - 3.3V the regulator framework will treat
that as a noop.  ...but that definitely doesn't appear to be the case.
When I boot up the first time even with no SD card plugged in, I see
this at bootup:

[    3.042234] vccio_sd: 1800 <--> 3300 mV at 3300 mV

...showing that it started at 3.3V.  Then I see:

$ grep "" /sys/class/regulator/regulator.16/{name,microvolts}
/sys/class/regulator/regulator.16/name:vccio_sd
/sys/class/regulator/regulator.16/microvolts:2700000

...so it is certainly getting changed even with no card plugged in.


BTW: I don't actually have one of these failing cards--all of mine
work.  Addy, do you know the make and model of the card you have that
fails?


-Doug

WARNING: multiple messages have this Message-ID (diff)
From: Doug Anderson <dianders@chromium.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "addy ke" <addy.ke@rock-chips.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Pawel Moll" <pawel.moll@arm.com>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
	"Kumar Gala" <galak@codeaurora.org>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"tgih.jun@samsung.com" <tgih.jun@samsung.com>,
	"Jaehoon Chung" <jh80.chung@samsung.com>,
	"Chris Ball" <chris@printf.net>,
	"Dinh Nguyen" <dinguyen@altera.com>,
	"Heiko Stübner" <heiko@sntech.de>,
	"Olof Johansson" <olof@lixom.net>,
	"Sonny Rao" <sonnyrao@chromium.org>,
	"Alexandru Stan" <amstan@chromium.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>, "open list":;
Subject: Re: [PATCH] mmc: dw_mmc: try pick the exact same voltage as vmmc for vqmmc
Date: Fri, 21 Nov 2014 09:42:08 -0800	[thread overview]
Message-ID: <CAD=FV=Ve1TY4+8quq1=18A1YOFvOWuFGrBmHLwMCwdWBSqzxOw@mail.gmail.com> (raw)
In-Reply-To: <CAPDyKFrzGfDew0eLLEcA+_iS_mo-O2bFU58fjirfXXA8AJ9UYQ@mail.gmail.com>

Ulf,

On Fri, Nov 21, 2014 at 4:06 AM, Ulf Hansson <ulf.hansson@linaro.org> wrote:
> [...]
>
>> Sure
>> If the first card is sd2.0 since startup, dw_mci_switch_voltage will not be called,
>
> That can't be right. mmc_power_up() should trigger
> dw_mci_switch_voltage() to be invoked.

Hmmm, I think you're right.  Addy: can you double check if it's only
the 2nd card for you?  I was thinking that if a regulator is currently
3.3V and you request 2.7 - 3.3V the regulator framework will treat
that as a noop.  ...but that definitely doesn't appear to be the case.
When I boot up the first time even with no SD card plugged in, I see
this at bootup:

[    3.042234] vccio_sd: 1800 <--> 3300 mV at 3300 mV

...showing that it started at 3.3V.  Then I see:

$ grep "" /sys/class/regulator/regulator.16/{name,microvolts}
/sys/class/regulator/regulator.16/name:vccio_sd
/sys/class/regulator/regulator.16/microvolts:2700000

...so it is certainly getting changed even with no card plugged in.


BTW: I don't actually have one of these failing cards--all of mine
work.  Addy, do you know the make and model of the card you have that
fails?


-Doug

WARNING: multiple messages have this Message-ID (diff)
From: dianders@chromium.org (Doug Anderson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: dw_mmc: try pick the exact same voltage as vmmc for vqmmc
Date: Fri, 21 Nov 2014 09:42:08 -0800	[thread overview]
Message-ID: <CAD=FV=Ve1TY4+8quq1=18A1YOFvOWuFGrBmHLwMCwdWBSqzxOw@mail.gmail.com> (raw)
In-Reply-To: <CAPDyKFrzGfDew0eLLEcA+_iS_mo-O2bFU58fjirfXXA8AJ9UYQ@mail.gmail.com>

Ulf,

On Fri, Nov 21, 2014 at 4:06 AM, Ulf Hansson <ulf.hansson@linaro.org> wrote:
> [...]
>
>> Sure
>> If the first card is sd2.0 since startup, dw_mci_switch_voltage will not be called,
>
> That can't be right. mmc_power_up() should trigger
> dw_mci_switch_voltage() to be invoked.

Hmmm, I think you're right.  Addy: can you double check if it's only
the 2nd card for you?  I was thinking that if a regulator is currently
3.3V and you request 2.7 - 3.3V the regulator framework will treat
that as a noop.  ...but that definitely doesn't appear to be the case.
When I boot up the first time even with no SD card plugged in, I see
this at bootup:

[    3.042234] vccio_sd: 1800 <--> 3300 mV at 3300 mV

...showing that it started at 3.3V.  Then I see:

$ grep "" /sys/class/regulator/regulator.16/{name,microvolts}
/sys/class/regulator/regulator.16/name:vccio_sd
/sys/class/regulator/regulator.16/microvolts:2700000

...so it is certainly getting changed even with no card plugged in.


BTW: I don't actually have one of these failing cards--all of mine
work.  Addy, do you know the make and model of the card you have that
fails?


-Doug

  parent reply	other threads:[~2014-11-21 17:42 UTC|newest]

Thread overview: 104+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30  2:21 [PATCH] mmc: dw_mmc: add a quirk for the defferent bit of sdio interrupt Addy Ke
2014-10-30  2:21 ` Addy Ke
2014-10-30  4:35 ` Jaehoon Chung
2014-10-30  4:35   ` Jaehoon Chung
2014-10-30  4:41 ` Doug Anderson
2014-10-30  4:41   ` Doug Anderson
2014-10-30  4:41   ` Doug Anderson
2014-10-30  4:49   ` Doug Anderson
2014-10-30  4:49     ` Doug Anderson
2014-10-30  4:49     ` Doug Anderson
2014-10-30  6:54     ` addy ke
2014-10-30  6:54       ` addy ke
2014-10-30 10:50 ` [PATCH] mmc: dw_mmc: add support for the other " Addy Ke
2014-10-30 10:50   ` Addy Ke
2014-10-30 11:02   ` Jaehoon Chung
2014-10-30 11:02     ` Jaehoon Chung
2014-10-31  0:46     ` addy ke
2014-10-31  0:46       ` addy ke
2014-10-31  1:14       ` Jaehoon Chung
2014-10-31  1:14         ` Jaehoon Chung
2014-10-30 11:11   ` Ulf Hansson
2014-10-30 11:11     ` Ulf Hansson
2014-10-30 11:11     ` Ulf Hansson
2014-10-30 11:17     ` Jaehoon Chung
2014-10-30 11:17       ` Jaehoon Chung
2014-10-30 11:17       ` Jaehoon Chung
2014-10-31  0:54       ` addy ke
2014-10-31  0:54         ` addy ke
2014-10-31  3:50   ` [PATCH v2] " Addy Ke
2014-10-31  3:50     ` Addy Ke
2014-10-31  5:14     ` Doug Anderson
2014-10-31  5:14       ` Doug Anderson
2014-10-31  5:14       ` Doug Anderson
2014-10-31  8:45     ` Jaehoon Chung
2014-10-31  8:45       ` Jaehoon Chung
2014-10-31  8:45       ` Jaehoon Chung
2014-10-31 15:55       ` Doug Anderson
2014-10-31 15:55         ` Doug Anderson
2014-10-31 15:55         ` Doug Anderson
2014-10-31 10:43     ` Heiko Stübner
2014-10-31 10:43       ` Heiko Stübner
2014-11-03  0:54       ` addy ke
2014-11-03  0:54         ` addy ke
2014-11-03  1:20   ` [PATCH v3] " Addy Ke
2014-11-03  1:20     ` Addy Ke
2014-11-03  8:59     ` Jaehoon Chung
2014-11-03  8:59       ` Jaehoon Chung
2014-11-03 10:23       ` addy ke
2014-11-03 10:23         ` addy ke
2014-11-04  2:14         ` Jaehoon Chung
2014-11-04  2:14           ` Jaehoon Chung
2014-11-03 10:23       ` Heiko Stübner
2014-11-03 10:23         ` Heiko Stübner
2014-11-04  2:15         ` Jaehoon Chung
2014-11-04  2:15           ` Jaehoon Chung
2014-11-04 14:03     ` [PATCH v4] " Addy Ke
2014-11-04 14:03       ` Addy Ke
2014-11-11  4:02       ` [PATCH] mmc: dw_mmc: try pick the exact same voltage as vmmc for vqmmc Addy Ke
2014-11-11  4:02         ` Addy Ke
2014-11-11  4:02         ` Addy Ke
2014-11-11  8:52         ` Ulf Hansson
2014-11-11  8:52           ` Ulf Hansson
2014-11-11  8:52           ` Ulf Hansson
2014-11-12 18:04           ` Doug Anderson
2014-11-12 18:04             ` Doug Anderson
2014-11-12 18:04             ` Doug Anderson
2014-11-13  2:19             ` addy ke
2014-11-13  2:19               ` addy ke
2014-11-21 12:06               ` Ulf Hansson
2014-11-21 12:06                 ` Ulf Hansson
2014-11-21 12:06                 ` Ulf Hansson
2014-11-21 12:29                 ` Jaehoon Chung
2014-11-21 12:29                   ` Jaehoon Chung
2014-11-21 12:29                   ` Jaehoon Chung
2014-11-21 17:42                 ` Doug Anderson [this message]
2014-11-21 17:42                   ` Doug Anderson
2014-11-21 17:42                   ` Doug Anderson
2014-11-21 21:04                   ` Doug Anderson
2014-11-21 21:04                     ` Doug Anderson
2014-11-21 21:04                     ` Doug Anderson
2014-11-24 13:29                     ` Ulf Hansson
2014-11-24 13:29                       ` Ulf Hansson
2014-11-24 13:29                       ` Ulf Hansson
2014-11-25  2:38                       ` Addy
2014-11-25  2:38                         ` Addy
2014-11-25  2:38                         ` Addy
2014-11-25  5:36                         ` Doug Anderson
2014-11-25  5:36                           ` Doug Anderson
2014-11-25  5:36                           ` Doug Anderson
2014-11-25 21:11                           ` Alexandru Stan
2014-11-25 21:11                             ` Alexandru Stan
2014-11-25 21:11                             ` Alexandru Stan
2014-11-25  5:29                       ` Doug Anderson
2014-11-25  5:29                         ` Doug Anderson
2014-11-25  5:29                         ` Doug Anderson
2014-11-13 18:58       ` [PATCH v4] mmc: dw_mmc: add support for the other bit of sdio interrupt Doug Anderson
2014-11-13 18:58         ` Doug Anderson
2014-11-13 18:58         ` Doug Anderson
2014-11-14 13:25         ` Jaehoon Chung
2014-11-14 13:25           ` Jaehoon Chung
2014-11-14 13:25           ` Jaehoon Chung
2014-11-19 10:32       ` Ulf Hansson
2014-11-19 10:32         ` Ulf Hansson
2014-11-19 10:32         ` 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='CAD=FV=Ve1TY4+8quq1=18A1YOFvOWuFGrBmHLwMCwdWBSqzxOw@mail.gmail.com' \
    --to=dianders@chromium.org \
    --cc=addy.ke@rock-chips.com \
    --cc=amstan@chromium.org \
    --cc=cf@rock-chips.com \
    --cc=chenfen@rock-chips.com \
    --cc=chris@printf.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@altera.com \
    --cc=galak@codeaurora.org \
    --cc=heiko@sntech.de \
    --cc=hj@rock-chips.com \
    --cc=hl@rock-chips.com \
    --cc=huangtao@rock-chips.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jh80.chung@samsung.com \
    --cc=kever.yang@rock-chips.com \
    --cc=lintao@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=olof@lixom.net \
    --cc=pawel.moll@arm.com \
    --cc=rdunlap@infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=sonnyrao@chromium.org \
    --cc=tgih.jun@samsung.com \
    --cc=ulf.hansson@linaro.org \
    --cc=xjq@rock-chips.com \
    --cc=yzq@rock-chips.com \
    --cc=zhangqing@rock-chips.com \
    --cc=zhenfu.fang@rock-chips.com \
    --cc=zyf@rock-chips.com \
    --cc=zyw@rock-chips.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.