[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D8EAF874-4FED-42EE-8FD8-E89B6CB0086A@collabora.com>
Date: Sat, 6 Sep 2025 09:04:04 -0300
From: Daniel Almeida <daniel.almeida@...labora.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>,
Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>,
Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>,
Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>,
linux-kernel@...r.kernel.org,
rust-for-linux@...r.kernel.org,
linux-usb@...r.kernel.org
Subject: Re: [PATCH 2/2] samples: rust: add a USB driver sample
Hi Greg,
[…]
>
> Sorry for the delay.
>
> But these bindings really are only for a usb interface probe/disconnect
> sequence, right? no real data flow at all?
>
> I recommend looking at the usb-skeleton.c driver, and implementing that
> as your sample driver for rust. That will ensure that you actually have
> the correct apis implemented and the reference count logic working
> properly. You have urb anchors and callbacks and other stuff as well to
> ensure that you get right. That driver pretty much should handle
> everything that you need to do to write a usb driver for any type of
> "real" device.
>
> thanks,
>
> greg k-h
I thought that an iterative approach would work here, i.e.: merge this, then
URBs, then more stuff, etc.
In any case that’s OK. I will work on the other stuff you listed here.
— Daniel
Powered by blists - more mailing lists