From: tgih.jun@samsung.com (Seungwon Jeon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] mmc: dw_mmc: use mmc_regulator_get_supply to handle regulators
Date: Fri, 27 Jun 2014 20:19:26 +0900 [thread overview]
Message-ID: <001201cf91f9$a7924920$f6b6db60$%jun@samsung.com> (raw)
In-Reply-To: <CAD=FV=VP6Exg-iJiAk=zNFpFzY8jFbU8HSR=wQQ7S+mfZWTJ=Q@mail.gmail.com>
On Fri, June 27, 2014, Doug Anderson wrote:
> Seungwon,
>
> On Thu, Jun 26, 2014 at 3:30 AM, Seungwon Jeon <tgih.jun@samsung.com> wrote:
> > Hi Doug,
> >
> > On Thu, June 26, 2014, Doug Anderson wrote:
> >> Seungwon,
> >>
> >> On Wed, Jun 25, 2014 at 4:18 AM, Seungwon Jeon <tgih.jun@samsung.com> wrote:
> >> >> >> + case MMC_POWER_ON:
> >> >> >> + if (!IS_ERR(mmc->supply.vqmmc) &&
> >> >> >> + !test_bit(DW_MMC_IO_POWERED, &slot->flags)) {
> >> > You can use regulator_is_enabled() instead of flag bit, DW_MMC_IO_POWERED.
> >>
> >> I'd be a little worried about regulator_is_enabled() since regulators
> >> are reference counted. What if someone else is sharing this
> >> regulator? The regulator might happen to be enabled when you check it
> >> but unless you add your own dw_mmc reference count they might turn it
> >> off.
> > Cool, that's a possibility. Some assumption may need.
> > If mmc's core can guarantee its balance, I think we don't need to consider some flag.
>
> I notice that the mmc core seems to keep a flag itself for vdd (the
> mmc->regulator_enabled flag). That would imply that the core thought
> it was important to have the extra flag and that we should keep our
> own flag for vqmmc.
Ok, Good.
Thanks,
Seungwon Jeon
>
> -Doug
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-06-27 11:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 10:45 [PATCH 0/3] Adding UHS support for dw_mmc driver Yuvaraj Kumar C D
2014-06-23 10:45 ` [PATCH 1/3] mmc: dw_mmc: use mmc_regulator_get_supply to handle regulators Yuvaraj Kumar C D
2014-06-24 18:00 ` Doug Anderson
2014-06-25 3:18 ` Jaehoon Chung
2014-06-25 4:00 ` Doug Anderson
2014-06-25 11:18 ` Seungwon Jeon
2014-06-25 17:28 ` Doug Anderson
2014-06-26 10:30 ` Seungwon Jeon
2014-06-26 16:20 ` Doug Anderson
2014-06-27 11:19 ` Seungwon Jeon [this message]
2014-06-26 11:21 ` Yuvaraj Kumar
2014-06-26 16:18 ` Doug Anderson
2014-06-27 10:59 ` Yuvaraj Kumar
2014-06-27 22:47 ` Doug Anderson
2014-07-22 19:31 ` Javier Martinez Canillas
2014-06-30 12:13 ` Jaehoon Chung
2014-06-30 15:06 ` Doug Anderson
2014-07-01 4:25 ` Jaehoon Chung
2014-06-23 10:45 ` [PATCH 2/3] mmc: dw_mmc: Dont cut off vqmmc and vmmc Yuvaraj Kumar C D
2014-06-24 18:10 ` Doug Anderson
2014-06-23 10:45 ` [PATCH 3/3] mmc: dw_mmc: Support voltage changes Yuvaraj Kumar C D
2014-06-24 18:17 ` Doug Anderson
2014-06-25 13:08 ` Seungwon Jeon
2014-06-25 17:46 ` Doug Anderson
2014-06-26 10:41 ` Seungwon Jeon
2014-06-26 16:50 ` Doug Anderson
2014-06-27 6:35 ` Yuvaraj Kumar
2014-06-27 11:18 ` Seungwon Jeon
2014-06-30 12:18 ` Jaehoon Chung
2014-07-01 11:17 ` Yuvaraj Kumar
2014-07-04 10:08 ` Seungwon Jeon
2014-07-07 5:23 ` Seungwon Jeon
2014-07-08 4:34 ` Yuvaraj Kumar
2014-07-08 9:56 ` Seungwon Jeon
2014-06-26 11:38 ` Yuvaraj Kumar
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='001201cf91f9$a7924920$f6b6db60$%jun@samsung.com' \
--to=tgih.jun@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).