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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Thu, 1 Feb 2024 15:53:48 +0530
From: Viken Dadhaniya <quic_vdadhani@...cinc.com>
To: Bryan O'Donoghue <pure.logic@...us-software.ie>, <andersson@...nel.org>,
        <konrad.dybcio@...aro.org>, <andi.shyti@...nel.org>,
        <linux-arm-msm@...r.kernel.org>, <linux-i2c@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <vkoul@...nel.org>,
        <quic_bjorande@...cinc.com>, <manivannan.sadhasivam@...aro.org>
CC: <quic_msavaliy@...cinc.com>, <quic_vtanuku@...cinc.com>
Subject: Re: [V2] i2c: i2c-qcom-geni: Correct I2C TRE sequence



On 1/30/2024 8:54 PM, Bryan O'Donoghue wrote:
> On 29/01/2024 06:10, Viken Dadhaniya wrote:
>> As per HPG(Hardware programming guide
> 
> Since you are doing a V3 here, please amend this too.
> 
> "As per HPG" means almost nothing outside of qcom.
> 
> "As per Qualcomm's internal Hardware Programming Guide"
> 
> Right thing to do to reference the document IMO but, you should make 
> clear its an internal silicon specification that's not public.
> 
> Also not sure the TRE description adds much.
> 
> Just give a high level description of the sequences being out-of-order 
> with respect to the hardware spec.
> 
> ---
> bod

Updated commit log and provided TRE description with sequence in V3.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ