linux-kernel - R: [PATCH 1/4] devicetree: bindings: pci: document tx-deempth tx swing and rx-eq property

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:   Tue, 14 Apr 2020 14:51:51 +0200
From:   <ansuelsmth@...il.com>
To:     "'Florian Fainelli'" <f.fainelli@...il.com>,
        <devicetree@...r.kernel.org>
Cc:     "'Mark Rutland'" <mark.rutland@....com>,
        "'Lorenzo Pieralisi'" <lorenzo.pieralisi@....com>,
        "'Richard Zhu'" <hongxing.zhu@....com>,
        "'Fabio Estevam'" <festevam@...il.com>,
        "'Sascha Hauer'" <s.hauer@...gutronix.de>,
        <linux-kernel@...r.kernel.org>,
        "'Rob Herring'" <robh+dt@...nel.org>,
        "'NXP Linux Team'" <linux-imx@....com>,
        "'Pengutronix Kernel Team'" <kernel@...gutronix.de>,
        <linux-pci@...r.kernel.org>,
        "'Bjorn Helgaas'" <bhelgaas@...gle.com>,
        "'Andrew Murray'" <amurray@...goodpenguin.co.uk>,
        "'Shawn Guo'" <shawnguo@...nel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        "'Lucas Stach'" <l.stach@...gutronix.de>
Subject: R: [PATCH 1/4] devicetree: bindings: pci: document tx-deempth tx swing and rx-eq property

> On 4/9/2020 5:47 PM, Ansuel Smith wrote:
> > Document tx-deempth, tx swing and rx-eq property property used on
> some
> > device (qcom ipq806x or imx6q) to tune and fix init error of the pci
> > bridge.
> 
> Those properties are not specific to the host bridge per-se, but to the
> PCIe PHY, therefore, one would expect to find those properties within
> the PCIe PHY node if it exists. Given you want this binding to be
> generic, this is an important thing to correct here.
> --
> Florian

So where should I put these? If I understand this properly I should move 
this to the PHY directory but no PCIe PHY node exist for both imx6q 
and ipq806x. How I should proceed? 
It would be better to just drop this and add qcom specific binding to the
driver?