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: Tue, 23 May 2017 10:44:32 +0200 [thread overview]
Message-ID: <1648498.2KlEJdsst9@phil> (raw)
In-Reply-To: <5610292.HlbkidXd60@phil>
Am Dienstag, 23. Mai 2017, 10:42:27 CEST schrieb Heiko Stuebner:
> Am Montag, 22. Mai 2017, 09:20:59 CEST schrieb Shawn Lin:
> > Hi Heiko,
> >
> > 在 2017/5/19 19:53, Heiko Stuebner 写道:
> > > 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@rock-chips.com>
> > >
> > > can these 2 patches really be independent?
> >
> > yes, they are sloving two different issues, so I think
> > they could be applied as-is.
> >
> > For patch 1, we was trying to ask PCI core to scan more
> > buses as possible, otherwise it now only scan one, which
> > isn't enough for PCIe switch chip.
> >
> > And before patch 2, we only allocated limited regions for
> > devices attached to our root bridge, so we will fail to enable
> > some devices if they ask more memory resource.
>
> ok, applied both for 4.13
just saw, that you may want to remember to include more people
in devicetree patches ... especially the linux-arm-kernel@lists.infradead.org
list. Doesn't hinder this patchset, but worth remembering for future series.
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2017-05-23 8:44 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 ` [PATCH 1/2] arm64: dts: extent bus-ranges " Heiko Stuebner
2017-05-22 1:20 ` 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 [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=1648498.2KlEJdsst9@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.