From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mmc: uniphier-sd: Add vqmmc regulator support
Date: Wed, 27 Sep 2017 17:50:47 +0200 [thread overview]
Message-ID: <cfaafd4a-bf4a-9174-4fc3-e0de62e0b51b@gmail.com> (raw)
In-Reply-To: <CAK7LNARrf5gf3+200h31H_anE8sP2=q1Zu_jLnPiWOn243sbkQ@mail.gmail.com>
On 09/27/2017 05:19 PM, Masahiro Yamada wrote:
> 2017-09-26 16:41 GMT+09:00 Jaehoon Chung <jh80.chung@samsung.com>:
>> Hi Marek,
>>
>> On 09/26/2017 01:47 AM, Marek Vasut wrote:
>>> On 09/15/2017 09:10 PM, Marek Vasut wrote:
>>>> Add initial support for setting the vqmmc regulator. Since we do not
>>>> support 1V8 modes, set the regulator to 3V3 and enable it.
>>>>
>>>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>>>> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
>>>> Cc: Jaehoon Chung <jh80.chung@samsung.com>
>>>
>>> Anything ?! I don't see this in the PR ...
>>
>> Sorry...I missed this patch..First, i have checked on patchwork.
>> Will pick this patch into u-boot-mmc.
>>
>> Best Regards,
>> Jaehoon Chung
>>
>
>
> UniPhier SoCs have different mechanism for 3.3/1.8 switching,
> but it is not a problem for me because I do not have a plan
> for enabling CONFIG_DM_REGULATOR.
>
> Acked-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Cool, thanks!
Is there a documentation for the uniphier mechanism somewhere ?
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2017-09-27 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 19:10 [U-Boot] [PATCH] mmc: uniphier-sd: Add vqmmc regulator support Marek Vasut
2017-09-25 16:47 ` Marek Vasut
2017-09-26 7:41 ` Jaehoon Chung
2017-09-27 15:19 ` Masahiro Yamada
2017-09-27 15:50 ` Marek Vasut [this message]
2017-09-27 16:13 ` Masahiro Yamada
2017-09-27 19:29 ` Marek Vasut
2017-09-29 2:30 ` Jaehoon Chung
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=cfaafd4a-bf4a-9174-4fc3-e0de62e0b51b@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.de \
/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