From: Paul Zimmerman <pauldzim@gmail.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH] hw/usb/hcd-dwc2: Simplified I/O memory regions
Date: Tue, 21 Apr 2020 12:13:25 -0700 [thread overview]
Message-ID: <4ab8a2f0-8b55-c96c-e827-3d3e739e7cc7@gmail.com> (raw)
In-Reply-To: <20200421071333.24706-1-f4bug@amsat.org>
On 4/21/20 12:13 AM, Philippe Mathieu-Daudé wrote:
> Use 1 container holding 2 regions:
> - I/O registers
> - FIFOs
>
> Remove all the static base addresses.
>
> Name address space.
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> Sometime a patch is cleaner/quicker than explanations.
> Suggestion to be squashed on patch:
> 'dwc-hsotg (dwc2) USB host controller emulation'
>
> Further simplificatio would be to move some exploded read/write
> functions directly into dwc2_hsotg_read/write.
>
> Based-on: <20200421014551.10426-1-pauldzim@gmail.com>
> ---
> hw/usb/hcd-dwc2.h | 17 +----
> hw/usb/hcd-dwc2.c | 181 ++++++++++++++++++++++------------------------
> 2 files changed, 88 insertions(+), 110 deletions(-)
<snip>
Ooh, yes, that looks much cleaner and simpler, thanks! I will test this
and fold it into the next version of the patch.
> static Property dwc2_usb_properties[] = {
> DEFINE_PROP_UINT32("usb_version", DWC2State, usb_version, 2),
> + /* FIXME isn't 'usb_version=2' const? */
This allows to switch between full-speed and high-speed at boot time,
which I've found very useful for testing purposes.
> + DEFINE_PROP_END_OF_LIST()
> };
>
> static void dwc2_class_init(ObjectClass *klass, void *data)
Thanks,
Paul
prev parent reply other threads:[~2020-04-21 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 7:13 [PATCH] hw/usb/hcd-dwc2: Simplified I/O memory regions Philippe Mathieu-Daudé
2020-04-21 19:13 ` Paul Zimmerman [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=4ab8a2f0-8b55-c96c-e827-3d3e739e7cc7@gmail.com \
--to=pauldzim@gmail.com \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--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).