Date: Thu, 10 Mar 2022 08:49:35 +0100 From: Hans Petter Selasky <hps@selasky.org> To: Farhan Khan <farhan@farhan.codes>, Daniel O'Connor <darius@dons.net.au> Cc: freebsd-usb@freebsd.org Subject: Re: Understanding USB callback + assertion panic Message-ID: <f978b307-9f54-9d74-97d7-c927831cc638@selasky.org> In-Reply-To: <1646869058201.32255222.1343660178@farhan.codes> References: <7abd641a74526552a8cc1692f7453cb3c1279034.camel@farhan.codes> <1646869058201.32255222.1343660178@farhan.codes>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/10/22 00:39, Farhan Khan wrote: > On Wednesday 09 March 2022 16:42:58 PM (-05:00), Farhan Khan wrote: > > > --------- > > error = usbd_transfer_setup(uaa->device, &iface_index, usc->usc_xfer, > > athn_config_common, ATHN_N_TRANSFERS, usc, &sc->sc_mtx); > > ATHN_LOCK(sc); > > usbd_transfer_start(usc->usc_xfer[ATHN_BULK_TX_DATA]); > > ATHN_UNLOCK(sc); > > --------- > > > > Considering this is quite similar to how other drivers do this, what > > might I be doing wrong? > > > > The mistake was on my end! My ATHN_LOCK code was incorrect and was not > actually locking the mutex. The issue was resolved and it works. > Thank you! I'm learning and making a lot of mistakes along the way. > Good to hear :-) --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f978b307-9f54-9d74-97d7-c927831cc638>