linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nadeem Athani <nadeem@cadence.com>
To: <tjoseph@cadence.com>, <bhelgaas@google.com>,
	<robh+dt@kernel.org>, <linux-pci@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<lorenzo.pieralisi@arm.com>, <robh@kernel.org>, <kishon@ti.com>
Cc: <mparab@cadence.com>, <sjakhade@cadence.com>,
	<nadeem@cadence.com>, <pthombar@cadence.com>
Subject: [PATCH 0/2] PCI: cadence: Set LTSSM Detect.Quiet state delay.
Date: Tue, 9 Mar 2021 08:31:40 +0100	[thread overview]
Message-ID: <20210309073142.13219-1-nadeem@cadence.com> (raw)

This patch includes a set of two patches.
First patch for adding a new property detect-quiet-min-delay in yaml file.
Second patch programs the delay value in host pcie driver.

The parameter detect-quiet-min-delay can be used to program the minimum
time that LTSSM waits on entering Detect.Quiet state.
00 : 0us minimum wait time in Detect.Quiet state.
01 : 100us minimum wait time in Detect.Quiet state.
10 : 1000us minimum wait time in Detect.Quiet state.
11 : 2000us minimum wait time in Detect.Quiet state.

Nadeem Athani (2):
  dt-bindings:pci: Set LTSSM Detect.Quiet state delay.
  PCI: cadence: Set LTSSM Detect.Quiet state delay.

 .../bindings/pci/cdns,cdns-pcie-host.yaml          | 13 +++++++++++++
 drivers/pci/controller/cadence/pcie-cadence-host.c | 22 ++++++++++++++++++++++
 drivers/pci/controller/cadence/pcie-cadence.h      | 10 ++++++++++
 3 files changed, 45 insertions(+)

-- 
2.15.0


             reply	other threads:[~2021-03-09  7:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09  7:31 Nadeem Athani [this message]
2021-03-09  7:31 ` [PATCH 1/2] dt-bindings:pci: Set LTSSM Detect.Quiet state delay Nadeem Athani
2021-03-09 16:46   ` Rob Herring
2021-03-14 18:56     ` Athani Nadeem Ladkhan
2021-03-09 17:19   ` Rob Herring
2021-03-09  7:31 ` [PATCH 2/2] PCI: cadence: " Nadeem Athani
2021-03-15 13:11   ` Kishon Vijay Abraham I

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=20210309073142.13219-1-nadeem@cadence.com \
    --to=nadeem@cadence.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mparab@cadence.com \
    --cc=pthombar@cadence.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sjakhade@cadence.com \
    --cc=tjoseph@cadence.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).