From: John Snow <jsnow@redhat.com>
To: Paul Zimmerman <pauldzim@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: Any interest in dwc-otg (aka dwc2) device emulation? For Raspi 3 and below.
Date: Tue, 10 Mar 2020 17:46:15 -0400 [thread overview]
Message-ID: <122351ec-88f8-cfbb-625a-5ff5d3f0f160@redhat.com> (raw)
In-Reply-To: <CADBGO7_GY8xO-QP73JzTgqAz_ZozT0Odv_WfrWDftuOmaRT96g@mail.gmail.com>
On 3/10/20 3:00 PM, Paul Zimmerman wrote:
> Hi Peter,
>
> I used to work for Synopsys, who is the vendor for the usb-otg IP, and
> am the author of the dwc2 driver in the Linux kernel (actually just a
> port of the vendor driver to Linux). So I am pretty familiar with the
> hardware. But I had to give up all the documentation when I left
> Synopsys. So, beyond what I could find on the web (register
> description and programming model), I don't have any further
> documentation.
>
> Thanks,
> Paul
>
That's awesome!
We don't always have specs for everything, but as many (public and
legal) references as you can spell out in your git commit messages, the
better, for the sake of maintainers who might need to audit changes in
the future (and don't have your expertise.)
Correlating things against the kernel driver will probably be plenty
good enough, I'd hope -- if the driver winds up having a bug against
real hardware we'd hope to see it in the wild, so it should be safe to
reference against.
(This is a bit of the snake eating its own tail but sometimes we just
don't have better.)
I wasn't aware you were the author of the kernel driver too. Now I'm
convinced it'd be a shame if you didn't at least post a v1!
--js
prev parent reply other threads:[~2020-03-10 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 0:34 Any interest in dwc-otg (aka dwc2) device emulation? For Raspi 3 and below Paul Zimmerman
2020-03-10 2:23 ` John Snow
2020-03-10 3:15 ` Paul Zimmerman
2020-03-10 9:52 ` Stefan Hajnoczi
2020-03-10 9:26 ` Peter Maydell
2020-03-10 19:00 ` Paul Zimmerman
2020-03-10 21:46 ` John Snow [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=122351ec-88f8-cfbb-625a-5ff5d3f0f160@redhat.com \
--to=jsnow@redhat.com \
--cc=f4bug@amsat.org \
--cc=pauldzim@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).