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: <5199fe6a-550a-4366-bee2-d4ab08ed248b@ixit.cz>
Date: Wed, 17 Dec 2025 16:00:36 +0100
From: David Heidelberg <david@...t.cz>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
 Bjorn Andersson <andersson@...nel.org>,
 Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, phone-devel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sdm845-oneplus: Enable known blocks and
 add placeholders

On 17/12/2025 13:04, Konrad Dybcio wrote:
> On 12/16/25 9:34 PM, David Heidelberg via B4 Relay wrote:
>> From: David Heidelberg <david@...t.cz>
>>
>> We know these devices are present; most of them are supported by
>> downstream and are close to the mainline kernels.
>>
>> This adds placeholders for:
>>   - front camera (imx371)
>>   - rear cameras (imx519, imx376k)
>>   - actuators
>>   - NFC node on i2c3
>>
>> This is very handy when rebasing the integration tree with
>> support for multiple different blocks at the same time.
>>
>> Signed-off-by: David Heidelberg <david@...t.cz>
>> ---
> 
> [...]
> 
>> +&i2c3 {
>> +	clock-frequency = <400000>;
>> +
>> +	status = "okay";
>> +
>> +	/* nxp,nxp-nci-i2c @28 */
> 
> This seems fairly straightforward to enable - could you just
> do that instead?

I have patch for it in-tree, but most likely not correct. See notes in:

https://gitlab.com/sdm845/sdm845-next/-/commit/eeb765bb1166e020a771ed712fec76b56da229ee

For now, I can only confirm the device is on the i2c address.

David>
> Konrad


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ