PCI: designware: Explain why we don't program ATU for some platforms
authorJisheng Zhang <jszhang@marvell.com>
Thu, 7 Jan 2016 06:12:38 +0000 (14:12 +0800)
committerBjorn Helgaas <bhelgaas@google.com>
Tue, 9 Feb 2016 18:38:51 +0000 (12:38 -0600)
commitdd193929d91e1b44b90f81509feeff10c94ddc4d
treec0bacadae9b24950f18968d7cc646524e6e7c9e3
parent92e963f50fc74041b5e9e744c330dca48e04f08d
PCI: designware: Explain why we don't program ATU for some platforms

Some platforms don't support ATU, e.g., pci-keystone.c.  These platforms
use their own address translation component rather than ATU, and they
provide the rd_other_conf and wr_other_conf methods to program the
translation component and perform the access.

Add a comment to explain why we don't program the ATU for these platforms.

[bhelgaas: changelog]
Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
drivers/pci/host/pcie-designware.c