From: Alan Stern <stern@rowland.harvard.edu>
To: Rhys Kidd <rhyskidd@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-usb@vger.kernel.org>,
<linux-accelerators@lists.ozlabs.org>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexander Shiyan <shc_work@mail.ru>,
Daniel Thompson <daniel.thompson@linaro.org>,
Johan Hovold <johan@kernel.org>
Subject: Re: [RFC PATCH 1/1] USB: myriad-ma24xx-vsc: Firmware loader driver for USB Myriad ma24xx
Date: Mon, 16 Sep 2019 11:28:18 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1909161127030.1489-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20190916110341.1310-2-rhyskidd@gmail.com>
On Mon, 16 Sep 2019, Rhys Kidd wrote:
> The Myriad ma24xx in USB Intel Neural Compute Stick and Intel Neural
> Compute Stick 2 provides an API to accelerate AI inference calculations
> on the dedicated SHAVE VLIW vector co-processors, which are orchestrated
> by one or more LEON SPARC v8 real time cores.
>
> However, they need firmware to be loaded beforehand. An uninitialised
> Myriad ma24xx presents with a distinctive USB ID. After firmware
> loading, the device detaches from the USB bus and reattaches with a new
> device ID. It can then be claimed by the usermode driver.
Is there any particular reason you need to have a kernel driver load
the firmware? Why can't a user program take care of it? The
usb_modeswitch program does that sort of thing all the time.
Alan Stern
next prev parent reply other threads:[~2019-09-16 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 11:03 [RFC PATCH 0/1] myriad-ma24xx-vsc: Helper fw driver for AI inference accelerator Rhys Kidd
2019-09-16 11:03 ` [RFC PATCH 1/1] USB: myriad-ma24xx-vsc: Firmware loader driver for USB Myriad ma24xx Rhys Kidd
2019-09-16 15:28 ` Alan Stern [this message]
2019-09-17 8:03 ` Oliver Neukum
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=Pine.LNX.4.44L0.1909161127030.1489-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=daniel.thompson@linaro.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-accelerators@lists.ozlabs.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=rhyskidd@gmail.com \
--cc=shc_work@mail.ru \
/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).