From: Bjorn Helgaas <bhelgaas@google.com>
To: Mohit Kumar <mohit.kumar@st.com>
Cc: jg1.han@samsung.com, Pratyush Anand <pratyush.anand@st.com>,
Arnd Bergmann <arnd@arndb.de>,
spear-devel@list.st.com, linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/1] Designware:RC BARs setup related fix
Date: Wed, 19 Feb 2014 14:53:59 -0700 [thread overview]
Message-ID: <20140219215359.GA19233@google.com> (raw)
In-Reply-To: <1392811475-17744-1-git-send-email-mohit.kumar@st.com>
On Wed, Feb 19, 2014 at 05:34:35PM +0530, Mohit Kumar wrote:
> The Synopsys PCIe core provides one pair of 32-bit BARs (BAR 0 and BAR 1).
> The BARs can be configured as follows:
>
> - One 64-bit BAR: BARs 0 and 1 are combined to form a single 64-bit BAR.
> - Two 32-bit BARs: BARs 0 and 1 are two independent 32-bit BARs
>
> This patch corrects 64-bit, non-prefetchable memory BAR configuration
> implemented in dw driver.
>
> Signed-off-by: Mohit Kumar <mohit.kumar@st.com>
> Cc: Pratyush Anand <pratyush.anand@st.com>
> Cc: Jingoo Han <jg1.han@samsung.com>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: spear-devel@list.st.com
> Cc: linux-pci@vger.kernel.org
Applied to pci/host-designware for v3.15, thanks!
I update the summary to the following; let me know if it's not accurate:
PCI: designware: Fix RC BAR to be single 64-bit non-prefetchable memory BAR
> ---
> drivers/pci/host/pcie-designware.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/pci/host/pcie-designware.c b/drivers/pci/host/pcie-designware.c
> index 17ce88f..6d23d8c 100644
> --- a/drivers/pci/host/pcie-designware.c
> +++ b/drivers/pci/host/pcie-designware.c
> @@ -800,7 +800,7 @@ void dw_pcie_setup_rc(struct pcie_port *pp)
>
> /* setup RC BARs */
> dw_pcie_writel_rc(pp, 0x00000004, PCI_BASE_ADDRESS_0);
> - dw_pcie_writel_rc(pp, 0x00000004, PCI_BASE_ADDRESS_1);
> + dw_pcie_writel_rc(pp, 0x00000000, PCI_BASE_ADDRESS_1);
>
> /* setup interrupt pins */
> dw_pcie_readl_rc(pp, PCI_INTERRUPT_LINE, &val);
> --
> 1.7.0.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-02-19 21:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 12:04 [PATCH 1/1] Designware:RC BARs setup related fix Mohit Kumar
2014-02-19 21:53 ` Bjorn Helgaas [this message]
2014-02-20 4:13 ` Mohit KUMAR DCG
2014-02-20 6:45 ` Mohit KUMAR DCG
2014-02-20 19:26 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2014-02-21 0:59 Jingoo Han
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=20140219215359.GA19233@google.com \
--to=bhelgaas@google.com \
--cc=arnd@arndb.de \
--cc=jg1.han@samsung.com \
--cc=linux-pci@vger.kernel.org \
--cc=mohit.kumar@st.com \
--cc=pratyush.anand@st.com \
--cc=spear-devel@list.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.