[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150519230532.GV31666@google.com>
Date: Tue, 19 May 2015 18:05:32 -0500
From: Bjorn Helgaas <bhelgaas@...gle.com>
To: Jisheng Zhang <jszhang@...vell.com>
Cc: jg1.han@...sung.com, Minghuan.Lian@...escale.com,
fabrice.gasnier@...com, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Mohit Kumar <mohit.kumar@...com>
Subject: Re: [PATCH v2 0/2] PCI: designware: improve iATU programming and
usage
[+cc Mohit]
On Thu, Apr 30, 2015 at 04:22:27PM +0800, Jisheng Zhang wrote:
> The outbound iATU programming functions are similar, so PATCH1 consolidates
> them into one.
>
> Most transactions' type are cfg0 and MEM, so current iATU usage is not
> balanced. PATCH2 adopts idea from Minghuan Lian <Minghuan.Lian@...escale.com>:
>
> http://www.spinics.net/lists/linux-pci/msg40440.html
>
> to change the iATU allocation: iATU0 for cfg and IO, iATU1 for MEM.
>
> Changes since v1:
> - remove outbound iATU programming for IO in dw_pcie_host_init, since it can
> be done by berlin_pcie_{rd|wr}_other_conf() latter.
> - only do outbound iATU programming for MEM if pp->ops->rd_other_conf is not
> set. Thank Fabrice Gasnier to point out "some platforms doesn't have support
> for ATU"
>
> Jisheng Zhang (2):
> PCI: designware: consolidate outbound iATU programming functions
> PCI: designware: use iATU0 for cfg and IO, iATU1 for MEM
>
> drivers/pci/host/pcie-designware.c | 142 ++++++++++++++++---------------------
These need acks from Jingoo and/or Mohit. Any opinions?
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists