From: Vidya Sagar <vidyas@nvidia.com>
To: "lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>
Cc: Jingoo Han <jingoohan1@gmail.com>,
"gustavo.pimentel@synopsys.com" <gustavo.pimentel@synopsys.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"amurray@thegoodpenguin.co.uk" <amurray@thegoodpenguin.co.uk>,
"robh@kernel.org" <robh@kernel.org>,
"treding@nvidia.com" <treding@nvidia.com>,
"jonathanh@nvidia.com" <jonathanh@nvidia.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kthota@nvidia.com" <kthota@nvidia.com>,
"mmaddireddy@nvidia.com" <mmaddireddy@nvidia.com>,
"sagar.tv@gmail.com" <sagar.tv@gmail.com>,
"Bjorn Helgaas" <helgaas@kernel.org>
Subject: Re: [PATCH V2] PCI: dwc: Add support to configure for ECRC
Date: Fri, 11 Dec 2020 19:28:25 +0530 [thread overview]
Message-ID: <49e3a6a4-9621-0734-99f1-b4f616dbcb7d@nvidia.com> (raw)
In-Reply-To: <42ebcbe2-7d24-558a-3c33-beb7818d5516@nvidia.com>
Hi Lorenzo,
Apologies to bug you, but wondering if you have any further comments on
this patch that I need to take care of?
Thanks,
Vidya Sagar
On 12/3/2020 5:40 PM, Vidya Sagar wrote:
>
>
> On 11/25/2020 2:32 AM, Bjorn Helgaas wrote:
>> External email: Use caution opening links or attachments
>>
>>
>> On Tue, Nov 24, 2020 at 03:50:01PM +0530, Vidya Sagar wrote:
>>> Hi Bjorn,
>>> Please let me know if this patch needs any further modifications
>>
>> I'm fine with it, but of course Lorenzo will take care of it.
> Thanks Bjorn.
>
> Hi Lorenzo,
> Please let me know if you have any comments for this patch.
>
> Thanks,
> Vidya Sagar
>
>>
>>> On 11/12/2020 10:32 PM, Vidya Sagar wrote:
>>>> External email: Use caution opening links or attachments
>>>>
>>>>
>>>> On 11/12/2020 3:59 AM, Bjorn Helgaas wrote:
>>>>> External email: Use caution opening links or attachments
>>>>>
>>>>>
>>>>> On Wed, Nov 11, 2020 at 10:21:46PM +0530, Vidya Sagar wrote:
>>>>>>
>>>>>>
>>>>>> On 11/11/2020 9:57 PM, Jingoo Han wrote:
>>>>>>> External email: Use caution opening links or attachments
>>>>>>>
>>>>>>>
>>>>>>> On 11/11/20, 7:12 AM, Vidya Sagar wrote:
>>>>>>>>
>>>>>>>> DesignWare core has a TLP digest (TD) override bit in
>>>>>>>> one of the control
>>>>>>>> registers of ATU. This bit also needs to be programmed for
>>>>>>>> proper ECRC
>>>>>>>> functionality. This is currently identified as an issue
>>>>>>>> with DesignWare
>>>>>>>> IP version 4.90a.
>>>>>>>>
>>>>>>>> Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
>>>>>>>> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
>>>>>>>> ---
>>>>>>>> V2:
>>>>>>>> * Addressed Bjorn's comments
>>>>>>>>
>>>>>>>> drivers/pci/controller/dwc/pcie-designware.c | 52
>>>>>>>> ++++++++++++++++++--
>>>>>>>> drivers/pci/controller/dwc/pcie-designware.h | 1 +
>>>>>>>> 2 files changed, 49 insertions(+), 4 deletions(-)
>>>>>>>>
>>>>>>>> diff --git
>>>>>>>> a/drivers/pci/controller/dwc/pcie-designware.c
>>>>>>>> b/drivers/pci/controller/dwc/pcie-designware.c
>>>>>>>> index c2dea8fc97c8..ec0d13ab6bad 100644
>>>>>>>> --- a/drivers/pci/controller/dwc/pcie-designware.c
>>>>>>>> +++ b/drivers/pci/controller/dwc/pcie-designware.c
>>>>>>>> @@ -225,6 +225,46 @@ static void
>>>>>>>> dw_pcie_writel_ob_unroll(struct dw_pcie *pci, u32 index,
>>>>>>>> u32 reg,
>>>>>>>> dw_pcie_writel_atu(pci, offset + reg, val);
>>>>>>>> }
>>>>>>>>
>>>>>>>> +static inline u32 dw_pcie_enable_ecrc(u32 val)
>>>>>>>
>>>>>>> What is the reason to use inline here?
>>>>>>
>>>>>> Actually, I wanted to move the programming part inside the
>>>>>> respective APIs
>>>>>> but then I wanted to give some details as well in comments so to
>>>>>> avoid
>>>>>> duplication, I came up with this function. But, I'm making it
>>>>>> inline for
>>>>>> better code optimization by compiler.
>>>>>
>>>>> I don't really care either way, but I'd be surprised if the compiler
>>>>> didn't inline this all by itself even without the explicit "inline".
>>>> I just checked it and you are right that compiler is indeed inlining it
>>>> without explicitly mentioning 'inline'.
>>>> I hope it is ok to leave it that way.
>>>>
>>>>>
>>>>>>>> +{
>>>>>>>> + /*
>>>>>>>> + * DesignWare core version 4.90A has this strange design
>>>>>>>> issue
>>>>>>>> + * where the 'TD' bit in the Control register-1 of
>>>>>>>> the ATU outbound
>>>>>>>> + * region acts like an override for the ECRC
>>>>>>>> setting i.e. the presence
>>>>>>>> + * of TLP Digest(ECRC) in the outgoing TLPs is
>>>>>>>> solely determined by
>>>>>>>> + * this bit. This is contrary to the PCIe spec
>>>>>>>> which says that the
>>>>>>>> + * enablement of the ECRC is solely determined by
>>>>>>>> the AER registers.
>>>>>>>> + *
>>>>>>>> + * Because of this, even when the ECRC is enabled through AER
>>>>>>>> + * registers, the transactions going through ATU
>>>>>>>> won't have TLP Digest
>>>>>>>> + * as there is no way the AER sub-system could
>>>>>>>> program the TD bit which
>>>>>>>> + * is specific to DesignWare core.
>>>>>>>> + *
>>>>>>>> + * The best way to handle this scenario is to program the
>>>>>>>> TD bit
>>>>>>>> + * always. It affects only the traffic from root
>>>>>>>> port to downstream
>>>>>>>> + * devices.
>>>>>>>> + *
>>>>>>>> + * At this point,
>>>>>>>> + * When ECRC is enabled in AER registers,
>>>>>>>> everything works normally
>>>>>>>> + * When ECRC is NOT enabled in AER registers, then,
>>>>>>>> + * on Root Port:- TLP Digest (DWord size) gets
>>>>>>>> appended to each packet
>>>>>>>> + * even through it is not required.
>>>>>>>> Since downstream
>>>>>>>> + * TLPs are mostly for
>>>>>>>> configuration accesses and BAR
>>>>>>>> + * accesses, they are not in
>>>>>>>> critical path and won't
>>>>>>>> + * have much negative effect on the
>>>>>>>> performance.
>>>>>>>> + * on End Point:- TLP Digest is received for
>>>>>>>> some/all the packets coming
>>>>>>>> + * from the root port. TLP Digest
>>>>>>>> is ignored because,
>>>>>>>> + * as per the PCIe Spec r5.0 v1.0 section
>>>>>>>> 2.2.3
>>>>>>>> + * "TLP Digest Rules", when an
>>>>>>>> endpoint receives TLP
>>>>>>>> + * Digest when its ECRC check
>>>>>>>> functionality is disabled
>>>>>>>> + * in AER registers, received TLP
>>>>>>>> Digest is just ignored.
>>>>>>>> + * Since there is no issue or error reported
>>>>>>>> either side, best way to
>>>>>>>> + * handle the scenario is to program TD bit by default.
>>>>>>>> + */
>>>>>>>> +
>>>>>>>> + return val | PCIE_ATU_TD;
>>>>>>>> +}
next prev parent reply other threads:[~2020-12-11 14:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 19:26 [PATCH] PCI: dwc: Add support to configure for ECRC Vidya Sagar
2020-11-10 20:50 ` Bjorn Helgaas
2020-11-11 12:11 ` [PATCH V2] " Vidya Sagar
2020-11-11 16:27 ` Jingoo Han
2020-11-11 16:51 ` Vidya Sagar
2020-11-11 22:29 ` Bjorn Helgaas
2020-11-12 17:02 ` Vidya Sagar
2020-11-24 10:20 ` Vidya Sagar
2020-11-24 21:02 ` Bjorn Helgaas
2020-12-03 12:10 ` Vidya Sagar
2020-12-11 13:58 ` Vidya Sagar [this message]
2020-12-11 14:49 ` Rob Herring
2020-12-11 15:15 ` Lorenzo Pieralisi
2020-12-11 16:54 ` Bjorn Helgaas
2020-12-11 17:17 ` Rob Herring
2020-12-07 14:18 ` [PATCH] " Rob Herring
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=49e3a6a4-9621-0734-99f1-b4f616dbcb7d@nvidia.com \
--to=vidyas@nvidia.com \
--cc=amurray@thegoodpenguin.co.uk \
--cc=bhelgaas@google.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=helgaas@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kthota@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mmaddireddy@nvidia.com \
--cc=robh@kernel.org \
--cc=sagar.tv@gmail.com \
--cc=treding@nvidia.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).