[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5bdd9ee6-86af-3bcc-43ff-418fd1a2e3e8@linux.intel.com>
Date: Tue, 6 Jul 2021 14:40:01 +0300
From: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
To: William Breathitt Gray <vilhelm.gray@...il.com>, jic23@...nel.org
Cc: linux-stm32@...md-mailman.stormreply.com, kernel@...gutronix.de,
a.fatoum@...gutronix.de, kamel.bouhara@...tlin.com,
gwendal@...omium.org, alexandre.belloni@...tlin.com,
david@...hnology.com, linux-iio@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
syednwaris@...il.com, patrick.havelange@...ensium.com,
fabrice.gasnier@...com, mcoquelin.stm32@...il.com,
alexandre.torgue@...com, o.rempel@...gutronix.de
Subject: Re: [PATCH v12 00/17] Introduce the Counter character device
interface
Hi
On 7/5/21 11:18 AM, William Breathitt Gray wrote:
> To summarize the main points of this patchset: there are no changes to
> the existing Counter sysfs userspace interface; a Counter character
> device interface is introduced that allows Counter events and associated
> data to be read() by userspace; the events_configure() and
> watch_validate() driver callbacks are introduced to support Counter
> events; and IRQ support is added to the 104-QUAD-8 driver, serving as an
> example of how to support the new Counter events functionality.
>
I quickly tested this set on top of linux-next next-20210706 and didn't
see any issue with intel-qep.c. However I noticed two mutex issues in
patch 15/17. Perhaps visible due the CONFIG_DEBUG_MUTEXES=y etc. I have on.
I'll be out of office next few weeks so cannot test if you have a new
version meanwhile but wanted to share no show stopper from intel-qep.c
and those two mutex warnings.
Jarkko
Powered by blists - more mailing lists