lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 20 Nov 2019 15:11:03 +0000
From:   Gustavo Pimentel <Gustavo.Pimentel@...opsys.com>
To:     Anvesh Salveru <anvesh.s@...sung.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:     "jingoohan1@...il.com" <jingoohan1@...il.com>,
        "gustavo.pimentel@...opsys.com" <Gustavo.Pimentel@...opsys.com>,
        "pankaj.dubey@...sung.com" <pankaj.dubey@...sung.com>,
        "lorenzo.pieralisi@....com" <lorenzo.pieralisi@....com>,
        "andrew.murray@....com" <andrew.murray@....com>,
        "bhelgaas@...gle.com" <bhelgaas@...gle.com>,
        "kishon@...com" <kishon@...com>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "mark.rutland@....com" <mark.rutland@....com>
Subject: RE: [PATCH v3 0/2] Add support to handle ZRX-DC Compliant PHYs

Hi,

You missed to sending this patch series to linux-pci@...r.kernel.org.

Regards,
Gustavo

On Wed, Nov 20, 2019 at 13:26:9, Anvesh Salveru <anvesh.s@...sung.com> 
wrote:

> 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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ