From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Rob Clark <robdclark@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
Andy Gross <agross@codeaurora.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Simon Horman <horms+renesas@verge.net.au>
Subject: Re: [PATCH] bus: SIMPLE_PM_BUS does not depend on ARCH_RENESAS
Date: Tue, 13 Jun 2017 09:39:59 -0700 [thread overview]
Message-ID: <20170613163959.GU12920@tuxbook> (raw)
In-Reply-To: <20170613130430.4272-1-robdclark@gmail.com>
+cc Geert, Simon, linux-pm
On Tue 13 Jun 06:04 PDT 2017, Rob Clark wrote:
> In fact, it is needed for PCI to work on msm8996 (and probably other
> things). No idea why it was depending on renesas but that doesn't make
> any sense. So drop the dependency.
>
This is in line with Geert's previous comments on how to utilize
simple-pm-bus to describe this hardware.
Acked-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Regards,
Bjorn
> Signed-off-by: Rob Clark <robdclark@gmail.com>
> ---
> drivers/bus/Kconfig | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/bus/Kconfig b/drivers/bus/Kconfig
> index 0a52da4..b83c535 100644
> --- a/drivers/bus/Kconfig
> +++ b/drivers/bus/Kconfig
> @@ -121,7 +121,6 @@ config QCOM_EBI2
> config SIMPLE_PM_BUS
> bool "Simple Power-Managed Bus Driver"
> depends on OF && PM
> - depends on ARCH_RENESAS || COMPILE_TEST
> help
> Driver for transparent busses that don't need a real driver, but
> where the bus controller is part of a PM domain, or under the control
> --
> 2.9.4
>
next parent reply other threads:[~2017-06-13 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170613130430.4272-1-robdclark@gmail.com>
2017-06-13 16:39 ` Bjorn Andersson [this message]
2017-06-16 20:01 ` [PATCH] bus: SIMPLE_PM_BUS does not depend on ARCH_RENESAS Simon Horman
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=20170613163959.GU12920@tuxbook \
--to=bjorn.andersson@linaro.org \
--cc=agross@codeaurora.org \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sboyd@codeaurora.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).