From: Kishon Vijay Abraham I <kishon@ti.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Pratyush Anand <pratyush.anand@st.com>,
Jingoo Han <jg1.han@samsung.com>,
'Bjorn Helgaas' <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
'Kukjin Kim' <kgene.kim@samsung.com>,
Mohit KUMAR DCG <Mohit.KUMAR@st.com>,
'Sean Cross' <xobs@kosagi.com>,
'Thierry Reding' <thierry.reding@gmail.com>,
'SRIKANTH TUMKUR SHIVANAND' <ts.srikanth@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH V3] pci: exynos: split into two parts such as Synopsys part and Exynos part
Date: Thu, 26 Sep 2013 10:36:45 +0530 [thread overview]
Message-ID: <5243C0E5.7020508@ti.com> (raw)
In-Reply-To: <201309242323.55323.arnd@arndb.de>
On Wednesday 25 September 2013 02:53 AM, Arnd Bergmann wrote:
> On Monday 23 September 2013, Kishon Vijay Abraham I wrote:
>> Btw if we hadn't programmed inbound translation table, the address will go
>> untranslated (according to the data book). I guess that's how it was working
>> for Jingoo Han.
>>
>> **
>> 3.10.4
>> Inbound iATU Operation
>>
>> When there is no match, then the address is untranslated
>> **
>>
>
> Well, that should work just as well, since you have a 1:1 translation anyway.
> Do you get the same error without the translation?
Yes. I get the same non-fatal error interrupt in RC.
Thanks
Kishon
next prev parent reply other threads:[~2013-09-26 5:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 5:21 [PATCH V3] pci: exynos: split into two parts such as Synopsys part and Exynos part Jingoo Han
2013-07-22 15:03 ` Kishon Vijay Abraham I
2013-07-23 1:14 ` Jingoo Han
2013-07-23 4:49 ` Pratyush Anand
2013-07-23 6:29 ` Kishon Vijay Abraham I
2013-07-23 7:00 ` Jingoo Han
2013-07-24 21:02 ` Arnd Bergmann
2013-09-12 6:34 ` Kishon Vijay Abraham I
2013-09-12 7:15 ` Jingoo Han
2013-09-12 9:30 ` Pratyush Anand
2013-09-12 9:43 ` Kishon Vijay Abraham I
2013-09-12 9:52 ` Pratyush Anand
2013-09-12 10:07 ` Kishon Vijay Abraham I
2013-09-12 10:18 ` Pratyush Anand
2013-09-12 10:46 ` Pratyush Anand
2013-09-12 11:14 ` Kishon Vijay Abraham I
2013-09-21 14:56 ` Kishon Vijay Abraham I
[not found] ` <523DB38B.4070307-l0cyMroinI0@public.gmane.org>
2013-09-21 22:03 ` Arnd Bergmann
[not found] ` <201309220003.34732.arnd-r2nGTMty4D4@public.gmane.org>
2013-09-22 11:16 ` Kishon Vijay Abraham I
2013-09-23 4:14 ` Pratyush Anand
2013-09-23 5:32 ` Kishon Vijay Abraham I
[not found] ` <523FD286.608-l0cyMroinI0@public.gmane.org>
2013-09-23 6:50 ` Pratyush Anand
2013-09-24 21:23 ` Arnd Bergmann
2013-09-26 5:06 ` Kishon Vijay Abraham I [this message]
2013-09-26 9:51 ` Arnd Bergmann
[not found] ` <201309261151.42034.arnd-r2nGTMty4D4@public.gmane.org>
2013-09-26 10:12 ` Kishon Vijay Abraham I
2013-09-12 10:25 ` Jingoo Han
2013-07-23 8:42 ` 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=5243C0E5.7020508@ti.com \
--to=kishon@ti.com \
--cc=Mohit.KUMAR@st.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=jg1.han@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=pratyush.anand@st.com \
--cc=thierry.reding@gmail.com \
--cc=ts.srikanth@samsung.com \
--cc=xobs@kosagi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).