From: Jiri Slaby <jirislaby@kernel.org>
To: Stuart <stuart.a.hayhurst@gmail.com>
Cc: linux-input@vger.kernel.org, Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] HID: corsair-void: Add Corsair Void headset family driver
Date: Mon, 10 Feb 2025 20:34:14 +0100 [thread overview]
Message-ID: <373c2d57-a513-4c2a-ae38-1aa01262c197@kernel.org> (raw)
In-Reply-To: <CALTg27meqwVyR_+doDzT6v-frx9hfy=fqkz-S2fTJpk8SMmThw@mail.gmail.com>
On 10. 02. 25, 19:31, Stuart wrote:
>> Not that easy, as AFAIR power unregister cannot sleep.
>
> Sorry, I'm not sure I follow, why would power_supply_unregister sleep?
> I thought the issue was about locking mutexes in an interrupt context,
> why wouldn't using spinlock_irqsave work instead?
There sure, but you want to protect the ->battery, right? So you'd need
to spin lock *also* power unregister.
Anyway, maybe I misunderstand, please send a patch and we will see ;).
--
js
suse labs
next prev parent reply other threads:[~2025-02-10 19:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 23:30 [PATCH v5] HID: corsair-void: Add Corsair Void headset family driver Stuart Hayhurst
2024-10-11 11:12 ` Jiri Kosina
2025-02-10 7:26 ` Jiri Slaby
2025-02-10 7:32 ` Jiri Slaby
2025-02-10 16:15 ` Stuart
2025-02-10 17:43 ` Jiri Slaby
2025-02-10 18:31 ` Stuart
2025-02-10 19:34 ` Jiri Slaby [this message]
2025-02-10 20:32 ` Stuart
2025-02-11 5:36 ` Jiri Slaby
2025-02-11 11:30 ` Stuart
2025-02-11 12:02 ` Jiri Slaby
2025-02-11 12:44 ` Stuart
2025-02-11 17:40 ` Jiri Slaby
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=373c2d57-a513-4c2a-ae38-1aa01262c197@kernel.org \
--to=jirislaby@kernel.org \
--cc=bentiss@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stuart.a.hayhurst@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).