From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 0/5] ARM: dts: rockchip: some regulator updates for popmetal and firefly
Date: Tue, 06 Oct 2015 10:27:56 +0200 [thread overview]
Message-ID: <2125379.ZDN8aXPFAA@phil> (raw)
In-Reply-To: <1443640670-21104-1-git-send-email-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
Am Mittwoch, 30. September 2015, 21:17:45 schrieb Heiko Stuebner:
> The upcoming mmc tuning definitly needs correct handling of the iodomains,
> which is also good to have in general. So this fixes some small regulator
> issues and then adds the io-domains for the rk3288 popmetal and firefly
> boards.
>
> Heiko Stuebner (5):
> ARM: dts: rockchip: add rk3288-popmetal board to dtb list
> ARM: dts: rockchip: add rk3288-popmemtal mmc supplies
> ARM: dts: rockchip: add rk3288-popmetal iodomains
> ARM: dts: rockchip: fixup firefly mmc supplies
> ARM: dts: rockchip: add rk3288-firefly iodomains
applied these to my dts branch for 4.4
prev parent reply other threads:[~2015-10-06 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 19:17 [PATCH 0/5] ARM: dts: rockchip: some regulator updates for popmetal and firefly Heiko Stuebner
[not found] ` <1443640670-21104-1-git-send-email-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2015-09-30 19:17 ` [PATCH 1/5] ARM: dts: rockchip: add rk3288-popmetal board to dtb list Heiko Stuebner
2015-09-30 19:17 ` [PATCH 2/5] ARM: dts: rockchip: add rk3288-popmemtal mmc supplies Heiko Stuebner
2015-09-30 19:17 ` [PATCH 3/5] ARM: dts: rockchip: add rk3288-popmetal iodomains Heiko Stuebner
2015-09-30 19:17 ` [PATCH 4/5] ARM: dts: rockchip: fixup firefly mmc supplies Heiko Stuebner
2015-09-30 19:17 ` [PATCH 5/5] ARM: dts: rockchip: add rk3288-firefly iodomains Heiko Stuebner
2015-10-06 8:27 ` Heiko Stuebner [this message]
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=2125379.ZDN8aXPFAA@phil \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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).