From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: multi_v7_defconfig: Enable Rockchip generic power domain.
Date: Mon, 14 Dec 2015 22:46:02 +0100 [thread overview]
Message-ID: <2469375.zETa3aloK0@diego> (raw)
In-Reply-To: <CAFqH_53DQ8GH+sq7PYeyDMT3qXJDBq+9P_4bCctMt_Sa_aXQBQ@mail.gmail.com>
Hi Enric,
defconfig changes are supposed to be applied by the armsoc maintainers, so you
should probably also include arm at kernel.org as real "To"
Am Montag, 14. Dezember 2015, 18:22:15 schrieben Sie:
> cc'ing: Heiko Stuebner (rockchip maintainer)
>
> 2015-12-14 18:17 GMT+01:00 Enric Balletbo i Serra <eballetbo@gmail.com>:
> > In order to meet high performance an low power requirement for Rockchip
> > enable the power domain support.
> >
I guess this should also mention the drm/kms issue (driver deferring until
power-domains are available) as further justification.
Otherwise, as I had experienced this myself while testing after we talked
about it:
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
> > Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> > ---
> >
> > arch/arm/configs/multi_v7_defconfig | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/arm/configs/multi_v7_defconfig
> > b/arch/arm/configs/multi_v7_defconfig index 69a22fd..81314ec 100644
> > --- a/arch/arm/configs/multi_v7_defconfig
> > +++ b/arch/arm/configs/multi_v7_defconfig
> > @@ -655,6 +655,7 @@ CONFIG_QCOM_PM=y
> >
> > CONFIG_QCOM_SMD=y
> > CONFIG_QCOM_SMD_RPM=y
> > CONFIG_QCOM_SMEM=y
> >
> > +CONFIG_ROCKCHIP_PM_DOMAINS=y
> >
> > CONFIG_COMMON_CLK_QCOM=y
> > CONFIG_CHROME_PLATFORMS=y
> > CONFIG_CROS_EC_CHARDEV=m
> >
> > --
> > 2.1.0
prev parent reply other threads:[~2015-12-14 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 17:17 [PATCH] ARM: multi_v7_defconfig: Enable Rockchip generic power domain Enric Balletbo i Serra
2015-12-14 17:22 ` Enric Balletbo Serra
2015-12-14 21:46 ` Heiko Stübner [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=2469375.zETa3aloK0@diego \
--to=heiko@sntech.de \
--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