linux-kernel - Re: [PATCH 4/5] dt-bindings: iio: proximity: hx9023s: support firmware-name 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20260209-active-quetzal-of-prowess-47a4ae@quoll>
Date: Mon, 9 Feb 2026 09:01:32 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Yasin Lee <yasin.lee.x@...il.com>
Cc: Jonathan Cameron <jic23@...nel.org>, 
	David Lechner <dlechner@...libre.com>, Nuno Sá <nuno.sa@...log.com>, 
	Andy Shevchenko <andy@...nel.org>, 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, linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 4/5] dt-bindings: iio: proximity: hx9023s: support
 firmware-name property

On Mon, Feb 09, 2026 at 11:37:05AM +0800, Yasin Lee wrote:
> Allow specifying the firmware file name via device tree.

For what purpose? What's in the firmware?

> 
> Signed-off-by: Yasin Lee <yasin.lee.x@...il.com>
> ---
>  Documentation/devicetree/bindings/iio/proximity/tyhx,hx9023s.yaml | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/iio/proximity/tyhx,hx9023s.yaml b/Documentation/devicetree/bindings/iio/proximity/tyhx,hx9023s.yaml
> index 64ce8bc8bd36..7e516fc011c6 100644
> --- a/Documentation/devicetree/bindings/iio/proximity/tyhx,hx9023s.yaml
> +++ b/Documentation/devicetree/bindings/iio/proximity/tyhx,hx9023s.yaml
> @@ -28,6 +28,12 @@ properties:
>  
>    vdd-supply: true
>  
> +  firmware-name:
> +    description:
> +      Name of the firmware file to be requested by the driver using
> +      the firmware loader interface.

Drop description, obvious. It cannot be anything else.

Best regards,
Krzysztof