From: Bjorn Helgaas <bhelgaas@google.com>
To: Jisheng Zhang <jszhang@marvell.com>
Cc: jg1.han@samsung.com, Minghuan.Lian@freescale.com,
fabrice.gasnier@st.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Mohit Kumar <mohit.kumar@st.com>
Subject: Re: [PATCH v2 0/2] PCI: designware: improve iATU programming and usage
Date: Tue, 19 May 2015 18:05:32 -0500 [thread overview]
Message-ID: <20150519230532.GV31666@google.com> (raw)
In-Reply-To: <1430382149-1645-1-git-send-email-jszhang@marvell.com>
[+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@freescale.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
WARNING: multiple messages have this Message-ID (diff)
From: bhelgaas@google.com (Bjorn Helgaas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] PCI: designware: improve iATU programming and usage
Date: Tue, 19 May 2015 18:05:32 -0500 [thread overview]
Message-ID: <20150519230532.GV31666@google.com> (raw)
In-Reply-To: <1430382149-1645-1-git-send-email-jszhang@marvell.com>
[+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@freescale.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
next prev parent reply other threads:[~2015-05-19 23:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 8:22 [PATCH v2 0/2] PCI: designware: improve iATU programming and usage Jisheng Zhang
2015-04-30 8:22 ` Jisheng Zhang
2015-04-30 8:22 ` [PATCH v2 1/2] PCI: designware: consolidate outbound iATU programming functions Jisheng Zhang
2015-04-30 8:22 ` Jisheng Zhang
2015-05-20 15:18 ` Pratyush Anand
2015-05-20 15:18 ` Pratyush Anand
2015-04-30 8:22 ` [PATCH v2 2/2] PCI: designware: use iATU0 for cfg and IO, iATU1 for MEM Jisheng Zhang
2015-04-30 8:22 ` Jisheng Zhang
2015-05-20 15:42 ` Pratyush Anand
2015-05-20 15:42 ` Pratyush Anand
2015-05-19 23:05 ` Bjorn Helgaas [this message]
2015-05-19 23:05 ` [PATCH v2 0/2] PCI: designware: improve iATU programming and usage Bjorn Helgaas
2015-05-19 23:21 ` Bjorn Helgaas
2015-05-19 23:21 ` Bjorn Helgaas
2015-05-20 20:03 ` Bjorn Helgaas
2015-05-20 20:03 ` Bjorn Helgaas
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=20150519230532.GV31666@google.com \
--to=bhelgaas@google.com \
--cc=Minghuan.Lian@freescale.com \
--cc=fabrice.gasnier@st.com \
--cc=jg1.han@samsung.com \
--cc=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mohit.kumar@st.com \
/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.