The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mauricio Faria de Oliveira <mfo@igalia.com>
To: Stanislaw Gruszka <stf_xl@wp.pl>
Cc: Matthieu CASTET <castet.matthieu@free.fr>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	kernel-dev@igalia.com, linux-atm-general@lists.sourceforge.net,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzbot+ce1e5a1b4e086b43e56d@syzkaller.appspotmail.com,
	syzbot+306212936b13e520679d@syzkaller.appspotmail.com
Subject: Re: [PATCH] usb: atm: ueagle-atm: use synchronous request_firmware()
Date: Fri, 22 May 2026 13:56:37 -0300	[thread overview]
Message-ID: <b540c25bcc62b0ed6f3dfa674c1c82d2@igalia.com> (raw)
In-Reply-To: <553f402beef6864520d0789f506fa4e2@igalia.com>

On 2026-05-18 12:54, Mauricio Faria de Oliveira wrote:
> On 2026-05-16 06:19, Stanislaw Gruszka wrote:
>> I prefer not to change this. If synchronization with disconnect
>> is required, I would rather keep request_firmware_nowait() and add 
>> explicit completion handling. Andrey some time ago posted a patch 
>> for this:
>> https://lore.kernel.org/lkml/20250410093146.3776801-1-aitsygunka@yandex.ru/
>> 
>> I refused the patch because it appears to only avoid pr_debug, but if
>> it fixes actual problem, we can take it.
> 
> Ok, I found it earlier, but opted otherwise as I missed the rationale.
> 
> I'll be happy to check it for resending; I had a slightly different
> implementation in mind when I considered a similar approach (using a
> struct completion in the existing data structure), but I'll double check
> it whether it's doable, and get back to you.

v2:
https://lore.kernel.org/all/20260522-ueagle-atm_req-fw-sync-v2-1-eee7f6b823a7@igalia.com/

This uses just struct usb_interface instead of a new structure, with
intfdata for struct completion and interface_to_usbdev() for struct
usb_device.

Also, use a condition check for pre-firmware devices in .disconnect(),
as IIUIC just 'else' could match interfaces != 0 on non pre-firmware
devices (i.e., bNumInterfaces != 1 && ifnum != 0).

Kind regards,
-- 
Mauricio

      reply	other threads:[~2026-05-22 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15 23:52 [PATCH] usb: atm: ueagle-atm: use synchronous request_firmware() Mauricio Faria de Oliveira
2026-05-16  9:19 ` Stanislaw Gruszka
2026-05-18 15:54   ` Mauricio Faria de Oliveira
2026-05-22 16:56     ` Mauricio Faria de Oliveira [this message]

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=b540c25bcc62b0ed6f3dfa674c1c82d2@igalia.com \
    --to=mfo@igalia.com \
    --cc=castet.matthieu@free.fr \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-dev@igalia.com \
    --cc=linux-atm-general@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stf_xl@wp.pl \
    --cc=syzbot+306212936b13e520679d@syzkaller.appspotmail.com \
    --cc=syzbot+ce1e5a1b4e086b43e56d@syzkaller.appspotmail.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