From: "Csókás Bence" <csokas.bence@prolan.hu>
To: William Breathitt Gray <wbg@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Kamel Bouhara <kamel.bouhara@bootlin.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<Dharma.B@microchip.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Jonathan Cameron <jic23@kernel.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v4 0/2] microchip-tcb-capture: Add Capture, Compare, Overflow etc. events
Date: Thu, 27 Feb 2025 16:56:17 +0100 [thread overview]
Message-ID: <077f23f1-3e5f-423c-aa97-ee7fcdf1475d@prolan.hu> (raw)
In-Reply-To: <Z8CKQvRjqH9lwzgO@ishi>
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
next prev parent reply other threads:[~2025-02-27 15:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 15:19 [PATCH v4 0/2] microchip-tcb-capture: Add Capture, Compare, Overflow etc. events Bence Csókás
2025-02-11 15:19 ` [PATCH v4 1/2] counter: microchip-tcb-capture: Add IRQ handling Bence Csókás
2025-02-11 15:19 ` [PATCH v4 2/2] counter: microchip-tcb-capture: Add capture extensions for registers RA-RC Bence Csókás
2025-02-21 12:39 ` [PATCH v4 0/2] microchip-tcb-capture: Add Capture, Compare, Overflow etc. events William Breathitt Gray
2025-02-21 14:14 ` Csókás Bence
2025-02-24 3:07 ` William Breathitt Gray
2025-02-26 12:58 ` Csókás Bence
2025-02-27 4:59 ` William Breathitt Gray
2025-02-27 13:53 ` Kamel Bouhara
2025-02-27 14:03 ` Kamel Bouhara
2025-02-27 14:22 ` William Breathitt Gray
2025-02-27 14:37 ` Alexandre Belloni
2025-02-27 15:12 ` William Breathitt Gray
2025-02-27 15:52 ` William Breathitt Gray
2025-02-27 15:56 ` Csókás Bence [this message]
2025-02-28 0:13 ` William Breathitt Gray
2025-02-27 17:36 ` Alexandre Belloni
2025-02-27 14:17 ` Csókás Bence
2025-02-27 15:00 ` William Breathitt Gray
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=077f23f1-3e5f-423c-aa97-ee7fcdf1475d@prolan.hu \
--to=csokas.bence@prolan.hu \
--cc=Dharma.B@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=jic23@kernel.org \
--cc=kamel.bouhara@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbg@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox