[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <077f23f1-3e5f-423c-aa97-ee7fcdf1475d@prolan.hu>
Date: Thu, 27 Feb 2025 16:56:17 +0100
From: Csókás Bence <csokas.bence@...lan.hu>
To: William Breathitt Gray <wbg@...nel.org>, Alexandre Belloni
<alexandre.belloni@...tlin.com>, Kamel Bouhara <kamel.bouhara@...tlin.com>
CC: <linux-arm-kernel@...ts.infradead.org>, <linux-iio@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <Dharma.B@...rochip.com>, Ludovic Desroches
<ludovic.desroches@...rochip.com>, Nicolas Ferre
<nicolas.ferre@...rochip.com>, Jonathan Cameron <jic23@...nel.org>, "Thomas
Petazzoni" <thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH v4 0/2] microchip-tcb-capture: Add Capture, Compare,
Overflow etc. events
Hi,
On 2025. 02. 27. 16:52, William Breathitt Gray wrote:
> Sorry, let me step back for a moment because maybe I'm trying to solve
> a problem that might not actually be a problem.
>
> I see functionality settings available in the TC Block Mode Register
> (BMR) that can affect multiple TCCs at a time. Are these BMR settings
> exposed already to users in someway? If not, do we have a way to
> introduce these settings if someone wants them; e.g. would the
> AutoCorrection function enable bit be exposed as a sysfs attribute, or
> configured in the devicetree?
>
> Finally, if there's not much interest in general for exposing these BMR
> settings, then I suppose there is no need to change how things are right
> now with the microchip-tcb-capture module and we can just keep it the
> way it is. That's my only concern, whether there are users that want to
> control these settings but don't have a way right now.
My knee-jerk answer to this is that if they do, they will bring it up by
submitting a patch or bug request. But I'll let others chime in, we only
use an extremely small subset of the features of the TCBs.
Bence
Powered by blists - more mailing lists