linux-kernel - Re: R: [PATCH v2 07/10] PCIe: qcom: fix init problem with missing PARF programming

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <2c5dcc8e-fc65-bc72-64c4-b5c69a21f7ca@mm-sol.com>
Date:   Wed, 8 Apr 2020 16:18:02 +0300
From:   Stanimir Varbanov <svarbanov@...sol.com>
To:     ansuelsmth@...il.com, 'Andy Gross' <agross@...nel.org>
Cc:     'Bjorn Andersson' <bjorn.andersson@...aro.org>,
        'Bjorn Helgaas' <bhelgaas@...gle.com>,
        'Rob Herring' <robh+dt@...nel.org>,
        'Mark Rutland' <mark.rutland@....com>,
        'Lorenzo Pieralisi' <lorenzo.pieralisi@....com>,
        'Andrew Murray' <amurray@...goodpenguin.co.uk>,
        'Philipp Zabel' <p.zabel@...gutronix.de>,
        linux-arm-msm@...r.kernel.org, linux-pci@...r.kernel.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: R: [PATCH v2 07/10] PCIe: qcom: fix init problem with missing
 PARF programming

Hi Ansuel,

On 4/8/20 3:38 PM, ansuelsmth@...il.com wrote:
>> PARF programming
>>
>> Hi Ansuel,
>>
>> Please fix the patch subject for all patches in the series per Bjorn H.
>> request.
>>
>> PCI: qcom: Fix init problem with missing PARF programming
>>
>> Also the patch subject is misleading to me. Actually you change few phy
>> parameters: Tx De-Emphasis, Tx Swing and Rx equalization. On the other
>> side I guess those parameters are board specific and I'm not sure how
>> this change will reflect on apq8064 boards.
>>
> 
> I also think that this would brake apq8064, on ipq8064 this is needed or 
> the system doesn't boot. 
> Should I move this to the dts and set this params only if they are present
> in dts or also here check for compatible and set accordingly? 
> 

I also think that these phy params should be per board (and they are
tunable).

Maybe you can propose those as generic phy params in pci.txt binding
document and then we can ask DT maintainers for opinion. If they refuse
such generic bindings, we could switch to custom qcom,phy properties.

-- 
regards,
Stan