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: <20241127215404.915-1-rafael.v.volkmer@gmail.com>
Date: Wed, 27 Nov 2024 18:54:04 -0300
From: "Rafael V. Volkmer" <rafael.v.volkmer@...il.com>
To: david@...hnology.com
Cc: linux-iio@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	rafael.v.volkmer@...il.com,
	wbg@...nel.org
Subject: Re: [PATCH] Add COUNTER_FUNCTION_DISABLE to the counter API

On 11/25/24 11:36 AM, David Lechner wrote:
> How does this work without an additional patch to modify the TI eQEP
> counter driver to handle this new enum value? For example, I would
> expect that this enum value would be added to ti_eqep_position_functions
> and case statements added in ti_eqep_function_read(),
> ti_eqep_function_write() and ti_eqep_action_read() to handle the new
> option.

Hi, David!

Yes, the intention is to have a second path where the eQEP driver handles 
this within these file operations functions.

Best regards

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ