Linux-Rockchip Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Shawn Lin <shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 1/2] arm64: dts: extent bus-ranges of PCIe for rk3399
Date: Fri, 19 May 2017 13:53:46 +0200	[thread overview]
Message-ID: <1839398.ekEOVhNgvp@phil> (raw)
In-Reply-To: <1494916241-75234-1-git-send-email-shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>

Hi Shawn,

Am Dienstag, 16. Mai 2017, 14:30:40 CEST schrieb Shawn Lin:
> In order to support multiple hierarchy of PCIe buses,
> for instance, PCIe switch, we need to extent bus-ranges
> to as max as possible. We have 32 regions and could support
> up to 31 buses except bus 0 for our root bridge.
> 
> Signed-off-by: Shawn Lin <shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>

can these 2 patches really be independent?

I.e. what happens if only this patch1 is applied and patch2 is not?
[important for bisectability]


Heiko

> ---
> 
>  arch/arm64/boot/dts/rockchip/rk3399.dtsi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> index 25cb51d..532b89d 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> @@ -220,7 +220,7 @@
>  		#size-cells = <2>;
>  		#interrupt-cells = <1>;
>  		aspm-no-l0s;
> -		bus-range = <0x0 0x1>;
> +		bus-range = <0x0 0x1f>;
>  		clocks = <&cru ACLK_PCIE>, <&cru ACLK_PERF_PCIE>,
>  			 <&cru PCLK_PCIE>, <&cru SCLK_PCIE_PM>;
>  		clock-names = "aclk", "aclk-perf",
> 

  parent reply	other threads:[~2017-05-19 11:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16  6:30 [PATCH 1/2] arm64: dts: extent bus-ranges of PCIe for rk3399 Shawn Lin
     [not found] ` <1494916241-75234-1-git-send-email-shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-05-16  6:30   ` [PATCH 2/2] arm64: dts: extent IORESOURCE_MEM_64 " Shawn Lin
2017-05-19 11:53   ` Heiko Stuebner [this message]
2017-05-22  1:20     ` [PATCH 1/2] arm64: dts: extent bus-ranges " Shawn Lin
     [not found]       ` <87486e22-2c42-a8a5-cd60-e6092dbecde7-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-05-23  8:42         ` Heiko Stuebner
2017-05-23  8:44           ` Heiko Stuebner

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=1839398.ekEOVhNgvp@phil \
    --to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
    --cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=shawn.lin-TNX95d0MmH7DzftRWevZcw@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