linux-kernel - Re: [PATCH v3 1/2] dt-bindings: iio: tyhx,hx9023s: Add performance tuning configuration

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]

Message-ID: <b59f6933-e1f1-49e9-be61-3e3b4323da87@gmail.com>
Date: Thu, 14 Nov 2024 23:16:51 +0800
From: Yasin Lee <yasin.lee.x@...il.com>
To: Jonathan Cameron <jic23@...nel.org>
Cc: Lars-Peter Clausen <lars@...afoo.de>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, yasin.lee.x@...look.com, linux-iio@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: tyhx,hx9023s: Add performance
 tuning configuration

On 10/20/24 21:06, Jonathan Cameron wrote:
> On Thu, 17 Oct 2024 18:36:44 +0800
> Yasin Lee <yasin.lee.x@...il.com> wrote:
>
>> When hardware design introduces significant sensor data noise,
>> performance can be improved by adjusting register settings.
> Questions inline. Mostly around why these controls belong in DT.
> What do they have to do with hardware / wiring etc rather than being
> appropriate for userspace controls.
>
> So almost all are definite no to being suitable for device tree bindings.
>
> Jonathan
>
Hi Jonathan,

Thank you for the suggestions in your recent email. Following your 
advice, I discussed these configurations in detail with engineers from 
the HX9023S supplier. Based on their feedback, these settings are not 
intended to be exposed to end-users. Typically, these configurations are 
adjusted during the DVT phase of the end product by the supplier to 
optimize performance, after which they are finalized and not meant to be 
modified dynamically at the user level.

Given this approach, it seems more appropriate to provide these settings 
as part of a firmware file, allowing the configuration to be kept 
internal and managed without user-level access. If this approach aligns 
with your thoughts, I can prepare and submit a new patch focused on 
firmware parsing and handling for these configurations.

Thank you again for your valuable guidance, and I look forward to your 
feedback.

Best regards,
Yasin Lee