All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leif Lindholm <quic_llindhol@quicinc.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Graeme Gregory <graeme@xora.org.uk>,
	<wangyuquan1236@phytium.com.cn>, <chenbaozi@phytium.com.cn>,
	<qemu-arm@nongnu.org>, <qemu-devel@nongnu.org>,
	Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH 1/1] hw/arm/sbsa-ref: use XHCI to replace EHCI
Date: Thu, 1 Jun 2023 18:59:56 +0100	[thread overview]
Message-ID: <ZHjcnHMWM9/Rl9lv@qc-i7.hemma.eciton.net> (raw)
In-Reply-To: <CAFEAcA_9Prr1xV2s1q2+GpWEnrsEEFT57bbLDnop5Hw3MaxM0A@mail.gmail.com>

+Ard

On Thu, Jun 01, 2023 at 16:01:43 +0100, Peter Maydell wrote:
> > >> Also has EHCI never worked, or has it worked in some modes and so this
> > >> change should be versioned?
> > >
> > > AIUI, EHCI has never worked and can never have worked, because
> > > this board's RAM is all above 4G and the QEMU EHCI controller
> > > implementation only allows DMA descriptors with 32-bit addresses.
> > >
> > > Looking back at the archives, it seems we discussed XHCI vs
> > > EHCI when the sbsa-ref board went in, and the conclusion was
> > > that XHCI would be better. But there wasn't a sysbus XHCI device
> > > at that point, so we ended up committing the sbsa-ref board
> > > with EHCI and a plan to switch to XHCI when the sysbus-xhci
> > > device was done, which we then forgot about:
> > > https://mail.gnu.org/archive/html/qemu-arm/2018-11/msg00638.html
> >
> > Ah, thanks! That explains why we did the thing that made no sense :)
> >
> > To skip the migration hazard, my prefernece is we just leave the EHCI
> > device in for now, and add a separate XHCI on PCIe. We can drop the
> > EHCI device at some point in the future.
> 
> Why PCIe for the XHCI and not sysbus? At the time the board
> was originally added the argument was in favour of using
> a sysbus USB controller (you can see Ard making that point
> in the linked archive thread).

The original argument was that having the device on the sysbus
1) enabled codepaths we wanted to exercise and
2) more closely resembled the development systems available at the
time.

1 still applies, but I'm not sure 2 does. Ard?

/
    Leif


  parent reply	other threads:[~2023-06-01 18:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31  7:02 [PATCH 0/1] hw/arm/sbsa-ref: use XHCI to replace EHCI wangyuquan1236
2023-05-31  7:02 ` [PATCH 1/1] " wangyuquan1236
2023-05-31 14:58   ` Graeme Gregory
2023-05-31 15:27     ` Peter Maydell
2023-05-31 16:23       ` Marcin Juszkiewicz
2023-05-31 16:36       ` Leif Lindholm
2023-05-31 17:12         ` Graeme Gregory
2023-06-01  2:37         ` Chen Baozi
2023-06-01 15:01         ` Peter Maydell
2023-06-01 15:30           ` Marcin Juszkiewicz
2023-06-01 16:39             ` Peter Maydell
2023-06-01 17:11               ` Marcin Juszkiewicz
2023-06-01 17:59           ` Leif Lindholm [this message]
2023-06-01 18:07             ` Ard Biesheuvel
2023-06-02  3:24             ` Yuquan Wang
2023-06-02  9:29               ` Leif Lindholm

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=ZHjcnHMWM9/Rl9lv@qc-i7.hemma.eciton.net \
    --to=quic_llindhol@quicinc.com \
    --cc=ardb@kernel.org \
    --cc=chenbaozi@phytium.com.cn \
    --cc=graeme@xora.org.uk \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wangyuquan1236@phytium.com.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.