From: Pratyush Anand <pratyush.anand@st.com>
To: <tj@kernel.org>
Cc: "Pedanekar, Hemant" <hemantp@ti.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Viresh KUMAR <viresh.kumar@st.com>,
Shiraz HASHIM <shiraz.hashim@st.com>,
Armando VISCONTI <armando.visconti@st.com>,
Vipin KUMAR <vipin.kumar@st.com>,
Deepak SIKRI <deepak.sikri@st.com>,
Rajeev KUMAR <rajeev-dlh.kumar@st.com>,
Vipul Kumar SAMAR <vipulkumar.samar@st.com>,
Amit VIRDI <Amit.VIRDI@st.com>,
Bhupesh SHARMA <bhupesh.sharma@st.com>
Subject: Re: [PATCH] PCIE: pcie_set_readrq must not be allowed by PCIE EP driver
Date: Thu, 23 Feb 2012 15:31:29 +0530 [thread overview]
Message-ID: <4F460E79.5000308@st.com> (raw)
In-Reply-To: <4D806132.1090704@st.com>
Hi Tejun,
Its a long pending patch.
Any decision on this patch.
Regards
Pratyush
On 3/16/2011 12:35 PM, pratyush wrote:
> Hello Hemant,
>
> On 3/16/2011 9:43 AM, Pedanekar, Hemant wrote:
>>> What happens in your case? Does it not work, if you do not
>>>> modify sil driver?
>>>>
>> I also require to modify the sil driver to avoid setting max RRQ to 4096
>> otherwise the data transfer over PCIe does not work. The RC responds with
>> "Unsupported Request" for read request of size greater than 256 bytes.
>>
>> The other problem is, there is no way for peers to know that the other
>> device cannot handle RRQ of size beyond certain limit. At least I am not
>> aware of any bits in PCIe configuration space which advertise this. Do you
>> know of any such?
>>
>> While, there is "Max RRQ size" field in device control register which only
>> controls outbound RRQ size.
>>
>> This restriction probbaly will complicate more when the device with such
>> RRQ limitation is a EP, in such case, no one else than the EP (and its driver)
>> would know about this limitation and need to force others (including RC) to
>> reduce the max RRQ size.
>>
>
> Yes, I am agreed with you. I do not see any way to inform its peers about request
> limit. So I think that a EP driver should not be allowed to call any function which
> changes EP's RRQ size. It should always be RC driver which sets these values as
> per max capability of the link.
>
> Currently I am managing it with postinit hook of RC driver. But can be part of
> common pci stack.
>
> You can see my way of handling it at
> http://www.spinics.net/lists/linux-pci/msg09897.html
>
> Regards
> Pratyush
next parent reply other threads:[~2012-02-23 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1297937650-2558-1-git-send-email-pratyush.anand@st.com>
[not found] ` <2A3DCF3DA181AD40BDE86A3150B27B6B0373799132@dbde02.ent.ti.com>
[not found] ` <2A3DCF3DA181AD40BDE86A3150B27B6B03737991EA@dbde02.ent.ti.com>
[not found] ` <4D78D6E3.50004@st.com>
[not found] ` <2A3DCF3DA181AD40BDE86A3150B27B6B03743048FE@dbde02.ent.ti.com>
[not found] ` <4D806132.1090704@st.com>
2012-02-23 10:01 ` Pratyush Anand [this message]
2012-02-23 17:42 ` [PATCH] PCIE: pcie_set_readrq must not be allowed by PCIE EP driver Tejun Heo
2012-02-24 3:57 ` Pratyush Anand
2012-02-24 5:38 ` Pedanekar, Hemant
2012-02-24 6:09 ` 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=4F460E79.5000308@st.com \
--to=pratyush.anand@st.com \
--cc=Amit.VIRDI@st.com \
--cc=armando.visconti@st.com \
--cc=bhupesh.sharma@st.com \
--cc=deepak.sikri@st.com \
--cc=hemantp@ti.com \
--cc=linux-pci@vger.kernel.org \
--cc=rajeev-dlh.kumar@st.com \
--cc=shiraz.hashim@st.com \
--cc=tj@kernel.org \
--cc=vipin.kumar@st.com \
--cc=vipulkumar.samar@st.com \
--cc=viresh.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 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).