linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anvesh Salveru <anvesh.s@samsung.com>
To: linux-kernel@vger.kernel.org
Cc: jingoohan1@gmail.com, gustavo.pimentel@synopsys.com,
	pankaj.dubey@samsung.com, lorenzo.pieralisi@arm.com,
	andrew.murray@arm.com, bhelgaas@google.com, kishon@ti.com,
	robh+dt@kernel.org, mark.rutland@arm.com,
	Anvesh Salveru <anvesh.s@samsung.com>
Subject: [PATCH v3 0/2] Add support to handle ZRX-DC Compliant PHYs
Date: Wed, 20 Nov 2019 18:56:09 +0530	[thread overview]
Message-ID: <1574256371-617-1-git-send-email-anvesh.s@samsung.com> (raw)
In-Reply-To: CGME20191120132645epcas5p29da16b1881e3da52fac0516a32e277d5@epcas5p2.samsung.com

According the PCI Express base specification when PHY does not meet
ZRX-DC specification, after every 100ms timeout the link should
transition to recovery state when the link is in low power states. 

Ports that meet the ZRX-DC specification for 2.5 GT/s while in the
L1.Idle state and are therefore not required to implement the 100 ms
timeout and transition to Recovery should avoid implementing it, since
it will reduce the power savings expected from the L1 state.

DesignWare controller provides GEN3_ZRXDC_NONCOMPL field in
GEN3_RELATED_OFF to specify about ZRX-DC compliant PHY.

We need to get the PHY property in controller driver. So, we are
proposing a new method phy_property_present() in the phy driver.

Platform specific phy drivers should implement the callback for
property_present which will return true if the property exists in
the PHY.

static bool xxxx_phy_property_present(struct phy *phy, const char *property)
{
       struct device *dev = &phy->dev;

       return of_property_read_bool(dev->of_node, property);
}

And controller platform driver should populate the phy_zrxdc_compliant
flag, which will be used by generic DesignWare driver.

pci->phy_zrxdc_compliant = phy_property_present(xxxx_ctrl->phy, "phy-zrxdc-compliant");

Anvesh Salveru (2):
  phy: core: add phy_property_present method
  PCI: dwc: add support to handle ZRX-DC Compliant PHYs

 drivers/pci/controller/dwc/pcie-designware.c |  6 ++++++
 drivers/pci/controller/dwc/pcie-designware.h |  4 ++++
 drivers/phy/phy-core.c                       | 26 ++++++++++++++++++++++++++
 include/linux/phy/phy.h                      |  8 ++++++++
 4 files changed, 44 insertions(+)

-- 
2.7.4


       reply	other threads:[~2019-11-20 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20191120132645epcas5p29da16b1881e3da52fac0516a32e277d5@epcas5p2.samsung.com>
2019-11-20 13:26 ` Anvesh Salveru [this message]
     [not found]   ` <CGME20191120132650epcas5p11fc132ba7084db7b7ad1b6c22b357770@epcas5p1.samsung.com>
2019-11-20 13:26     ` [PATCH v3 1/2] phy: core: add phy_property_present method Anvesh Salveru
     [not found]   ` <CGME20191120132657epcas5p418542be130de4e02901825eeac7edcdb@epcas5p4.samsung.com>
2019-11-20 13:26     ` [PATCH v3 2/2] PCI: dwc: add support to handle ZRX-DC Compliant PHYs Anvesh Salveru
2019-11-20 15:11   ` [PATCH v3 0/2] Add " Gustavo Pimentel

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=1574256371-617-1-git-send-email-anvesh.s@samsung.com \
    --to=anvesh.s@samsung.com \
    --cc=andrew.murray@arm.com \
    --cc=bhelgaas@google.com \
    --cc=gustavo.pimentel@synopsys.com \
    --cc=jingoohan1@gmail.com \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=pankaj.dubey@samsung.com \
    --cc=robh+dt@kernel.org \
    /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).