From: Marek Vasut <marex@denx.de>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Mohit KUMAR DCG <Mohit.KUMAR@st.com>,
Jingoo Han <jg1.han@samsung.com>,
"'Bjorn Helgaas'" <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Pratyush ANAND <pratyush.anand@st.com>,
"'Richard Zhu'" <r65037@freescale.com>
Subject: Re: [PATCH] PCI: designware: Remove unnecessary RC BAR setting
Date: Wed, 2 Apr 2014 12:34:47 +0200 [thread overview]
Message-ID: <201404021234.48134.marex@denx.de> (raw)
In-Reply-To: <533BA157.6030004@ti.com>
On Wednesday, April 02, 2014 at 07:34:15 AM, Kishon Vijay Abraham I wrote:
> On Wednesday 02 April 2014 11:03 AM, Mohit KUMAR DCG wrote:
> > Hello Jingoo,
> >
> >> -----Original Message-----
> >> From: Jingoo Han [mailto:jg1.han@samsung.com]
> >> Sent: Wednesday, April 02, 2014 10:53 AM
> >> To: Mohit KUMAR DCG
> >> Cc: 'Bjorn Helgaas'; linux-pci@vger.kernel.org; Pratyush ANAND; 'Marek
> >> Vasut'; 'Richard Zhu'; 'Kishon Vijay Abraham I'
> >> Subject: Re: [PATCH] PCI: designware: Remove unnecessary RC BAR setting
> >>
> >> On Wednesday, April 02, 2014 1:57 PM, Mohit KUMAR DCG wrote:
> >>> On Tuesday, April 01, 2014 4:00 PM, Jingoo Han wrote:
> >>>> According to the spec, the synopsys core does not implement the
> >>>> optional BARs such as BAR0/1. This is based on the assumption that
> >>>> the RC host probably has registers on some other internal bus and
> >>>> has knowledge and setup access to these registers already.
> >>>> So, remove unnecessary RC BAR setting.
> >>>
> >>> - Normally BARs in RC are not used but somehow available in the
> >>> design. One possible BAR use can be if RC has some memory connected to
> >>
> >> the BAR that needs to be accessed through link.
> >>
> >>> Otherwise we can ignore BARs setup here.
> >>
> >> Hi Mohit KUMAR DCG,
> >>
> >> Thank you for your feedback.
> >>
> >> I want to know whether or not other SoCs such as ST, Freescale, TI
> >> support BAR0/BAR1. If no SoC supports BAR0/BAR1, the unnecessary RC BAR
> >> setting code should be removed.
> >
> > - We are not currently using RC's BAR0/1 in any application but no such
> > restriction from HW as ST SoCs support BARs in HW design.
>
> Neither do we in DRA7xx.
I suspect that means we should keep the code to make sure the registers are
configured correctly, no?
Richard, can you comment on MX6 please ?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-04-02 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 10:30 [PATCH] PCI: designware: Remove unnecessary RC BAR setting Jingoo Han
2014-04-02 4:57 ` Mohit KUMAR DCG
2014-04-02 5:22 ` Jingoo Han
2014-04-02 5:33 ` Mohit KUMAR DCG
2014-04-02 5:34 ` Kishon Vijay Abraham I
2014-04-02 10:34 ` Marek Vasut [this message]
2014-04-02 11:58 ` Hong-Xing.Zhu
2014-04-04 2:31 ` Jingoo Han
2014-04-24 21:35 ` Bjorn Helgaas
2014-04-25 1:04 ` 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=201404021234.48134.marex@denx.de \
--to=marex@denx.de \
--cc=Mohit.KUMAR@st.com \
--cc=bhelgaas@google.com \
--cc=jg1.han@samsung.com \
--cc=kishon@ti.com \
--cc=linux-pci@vger.kernel.org \
--cc=pratyush.anand@st.com \
--cc=r65037@freescale.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.