From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: "Uwe Kleine-König" <ukleinek@kernel.org>,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org,
"Benjamin Larsson" <benjamin.larsson@genexis.eu>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Lorenzo Bianconi" <lorenzo@kernel.org>
Subject: Re: [PATCH v18] pwm: airoha: Add support for EN7581 SoC
Date: Fri, 27 Jun 2025 13:25:48 +0300 [thread overview]
Message-ID: <aF5xrHkTr8Tb71ZH@smile.fi.intel.com> (raw)
In-Reply-To: <685e6544.5d0a0220.20cf55.9440@mx.google.com>
On Fri, Jun 27, 2025 at 11:32:46AM +0200, Christian Marangi wrote:
> On Fri, Jun 27, 2025 at 11:58:04AM +0300, Andy Shevchenko wrote:
> > On Fri, Jun 27, 2025 at 12:47:53AM +0200, Christian Marangi wrote:
...
> > > + /* Global mutex to protect bucket used refcount_t */
> > > + struct mutex mutex;
> >
> > This makes a little sense. Either you use refcount_t (which is atomic) or
> > use mutex + regular variable.
>
> Using a regular variable I lose all the benefits of refcount_t with
> underflow and other checks.
Then drop the mutex, atomic operations do not need an additional
synchronisation. Btw, have you looked at kref APIs? Maybe that
would make the intention clearer?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-06-27 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 22:47 [PATCH v18] pwm: airoha: Add support for EN7581 SoC Christian Marangi
2025-06-27 8:58 ` Andy Shevchenko
2025-06-27 9:32 ` Christian Marangi
2025-06-27 10:25 ` Andy Shevchenko [this message]
2025-06-27 10:34 ` Christian Marangi
2025-06-27 10:56 ` Andy Shevchenko
2025-06-30 10:19 ` Christian Marangi
2025-06-30 10:29 ` Andy Shevchenko
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=aF5xrHkTr8Tb71ZH@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ansuelsmth@gmail.com \
--cc=benjamin.larsson@genexis.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=ukleinek@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.