qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "kraxel@redhat.com" <kraxel@redhat.com>,
	Sai Pavan Boddu <saipava@xilinx.com>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: sysbus usb xhci
Date: Thu, 2 Jan 2020 12:26:19 +0100	[thread overview]
Message-ID: <b8ad0f98-a02d-bcb2-acd8-a6e9fb606167@redhat.com> (raw)
In-Reply-To: <20200102094515.bbjaqlif7ucvzuou@sirius.home.kraxel.org>

On 1/2/20 10:45 AM, kraxel@redhat.com wrote:
> On Thu, Jan 02, 2020 at 07:13:25AM +0000, Sai Pavan Boddu wrote:
>> Hi Gred,
>>
>> We are seeing of options to reuse the hcd-xhci model and use it over system bus interface rather than pci. (for Xilinx ZynqMP SOC, usb emulation)
>> Are there any plans of implementing a sysbus device ? if none it would be good if provided few pointers to start.
> 
> There have been some discussions about this for a (IIRC) sbsa machine,
> but I'm not sure whenever that where just ideas or some code exists.
> 
>> Im looking at hcd-ehci/ochi as a reference, let me know if there are any know limitations for this usecase.
> 
> Yep, the path for xhci would be quite simliar:  Create a new
> XHCIPciState struct, move over all pci-specific bits from XHCIState,
> leaving the generic stuff in XHCIState for sharing with sysbus.
> Possibly move all pci-specific code bits into a new source file (for
> cleanup, will also allow to build qemu with CONFIG_PCI=n and still have
> XHCI enabled).
> 
> Once this separation is done you should be able to create a sysbus
> device, reusing the generic xhci code and adding sysbus plumbing
> (mmio, irq, ...)

The SDHCI commits b635d98cf32..8b7455c75e seem similar to what you want 
to achieve (see also commit ce8646034).



  reply	other threads:[~2020-01-02 11:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02  7:13 sysbus usb xhci Sai Pavan Boddu
2020-01-02  9:45 ` kraxel
2020-01-02 11:26   ` Philippe Mathieu-Daudé [this message]
2020-01-03  5:14     ` Sai Pavan Boddu
2020-01-08 15:32       ` Sai Pavan Boddu
2020-01-08 15:51         ` Philippe Mathieu-Daudé
2020-01-17 15:46           ` Sai Pavan Boddu

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=b8ad0f98-a02d-bcb2-acd8-a6e9fb606167@redhat.com \
    --to=philmd@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=saipava@xilinx.com \
    /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).