linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Mohit KUMAR DCG <Mohit.KUMAR@st.com>,
	"jg1.han@samsung.com" <jg1.han@samsung.com>
Cc: Ajay KHANDELWAL <ajay.khandelwal@st.com>,
	Bjorn Helgaas <bhelgass@google.com>,
	spear-devel <spear-devel@list.st.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 2/2] PCI:designware:Fix iATU programming for cfg1, io and mem viewport
Date: Thu, 20 Feb 2014 17:43:08 +0530	[thread overview]
Message-ID: <5305F154.8020507@ti.com> (raw)
In-Reply-To: <2CC2A0A4A178534D93D5159BF3BCB66189FD40D8B3@EAPEX1MAIL1.st.com>

Hi Mohit,

On Thursday 20 February 2014 05:28 PM, Mohit KUMAR DCG wrote:
> Hello Kishon,
> 
>> -----Original Message-----
>> From: Kishon Vijay Abraham I [mailto:kishon@ti.com]
>> Sent: Thursday, February 20, 2014 5:08 PM
>> To: Mohit KUMAR DCG; jg1.han@samsung.com
>> Cc: Ajay KHANDELWAL; Bjorn Helgaas; spear-devel; linux-
>> pci@vger.kernel.org
>> Subject: Re: [PATCH 2/2] PCI:designware:Fix iATU programming for cfg1, io
>> and mem viewport
>>
>> Hi,
>>
>> On Thursday 20 February 2014 10:52 AM, Mohit Kumar wrote:
>>> This patch correct iATU programming for cfg1, io and mem viewport.
>>> Enable ATU only after configuring it.
>>
>> Does this patch actually fixes device enumeration behind a PCIe-pci bridge or
>> this is more of cleaning up the sequence?
>>
> - This patch corrects ATU programming sequence. I am not aware of any such issue with
> current driver. Pls specify  which bridge do you use in your setup and what is the problem?

I tried with card [1], it had a PLX bridge chip. It couldn't read the
configuration space of the device connected to the PCIe-PCI bridge.

Thanks
Kishon

[1] -> http://ratetorate.in/products/Wiretech-PCIe%252dto%252dPCI-Bridge-Card.

> 
> Regards
> Mohit
> 


  reply	other threads:[~2014-02-20 12:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20  5:22 [PATCH 1/2] PCI:designware:Fix comment for setting number of lanes Mohit Kumar
2014-02-20  5:22 ` [PATCH 2/2] PCI:designware:Fix iATU programming for cfg1, io and mem viewport Mohit Kumar
2014-02-20  6:45   ` Mohit KUMAR DCG
2014-02-20 11:38   ` Kishon Vijay Abraham I
2014-02-20 11:58     ` Mohit KUMAR DCG
2014-02-20 12:13       ` Kishon Vijay Abraham I [this message]
2014-02-20 13:33         ` Mohit KUMAR DCG
2014-02-21  3:54         ` Pratyush Anand
2014-02-20  6:56 ` [PATCH 1/2] PCI:designware:Fix comment for setting number of lanes Rajeev kumar
2014-02-20  8:29   ` Mohit KUMAR DCG
  -- strict thread matches above, loose matches on Subject: below --
2014-02-21  1:31 [PATCH 2/2] PCI:designware:Fix iATU programming for cfg1, io and mem viewport Jingoo Han
2014-02-21  5:28 ` Kishon Vijay Abraham I
2014-02-26  6:31   ` Ajay Khandelwal
2014-02-26  7:47     ` Kishon Vijay Abraham I
2014-02-26 10:52       ` Pratyush Anand
2014-02-27  1:18         ` Jingoo Han
2014-02-27  1:37           ` Jingoo Han
2014-02-27  4:10             ` Pratyush Anand

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=5305F154.8020507@ti.com \
    --to=kishon@ti.com \
    --cc=Mohit.KUMAR@st.com \
    --cc=ajay.khandelwal@st.com \
    --cc=bhelgass@google.com \
    --cc=jg1.han@samsung.com \
    --cc=linux-pci@vger.kernel.org \
    --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 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).