summaryrefslogtreecommitdiff
path: root/sound/soc/nuc900
diff options
context:
space:
mode:
authorShawn Lin <shawn.lin@rock-chips.com>2017-03-20 10:38:00 +0800
committerHeiko Stuebner <heiko@sntech.de>2017-03-22 17:50:09 +0100
commit41b464ef10219e45513d1bcaddacd47ce0bd6136 (patch)
tree9f31ba54fb46dc4f5e5e79e1cfeeecdf1531acc2 /sound/soc/nuc900
parent04dc7f62037b0d3aead0dc62231efad89affa9f3 (diff)
arm64: dts: rockchip: fix PCIe domain number for rk3399
It's suggested to fix the domain number for all PCIe host bridges or not set it at all. However, if we don't fix it, the domain number will keep increasing ever when doing unbind/bind test, which makes the bus tree of lspci introduce pointless domain hierarchy. More investigation shows the domain number allocater of PCI doesn't consider the conflict of domain number if we have more than one PCIe port belonging to different domains. So once unbinding/binding one of them and keep others would going to overflow the domain number so that finally it will share the same domain as others, but actually it shouldn't. We should fix the domain number for PCIe or invent new indexing ID mechanisms. However it isn't worth inventing new indexing ID mechanisms personlly, Just look at how other Root Complex drivers did, for instance, broadcom and qualcomm, it seems fixing the domain number was more popular. So this patch gonna fix the domain number of PCIe for rk3399. Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com> Reviewed-by: Brian Norris <briannorris@chromium.org> Tested-by: Brian Norris <briannorris@chromium.org> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Diffstat (limited to 'sound/soc/nuc900')
0 files changed, 0 insertions, 0 deletions