From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH v2 0/4] usb: xhci: Prepare xHCI driver for MIPS Octeon big-endian support
Date: Tue, 21 Jul 2020 10:46:01 +0200 [thread overview]
Message-ID: <20200721084605.3801454-1-sr@denx.de> (raw)
These patches fix a few issues, found while porting the xHCI to the MIPS
Octeon platforms. The basic issues here are:
- Endianess issues: missing cpu_to_leXX() & leXX_to_cpu() conversions
- Use physical (DMA) address for the xHCI DMA controller
These patches are the groundwork for the upcoming xHCI Octeon support
that will follow soon.
Thanks,
Stefan
Changes in v2:
- Add missing (uintptr_t) cast to remove compile time warning
Stefan Roese (4):
usb: xhci: Add missing endian conversions (cpu_to_leXX / leXX_to_cpu)
usb: xhci: xhci_mem_init: Use cpu_to_le64() and not xhci_writeq()
usb: usb-uclass.c: Drop le16_to_cpu() as values are already swapped
usb: xhci: Add virt_to_phys() to support mapped platforms
drivers/usb/host/usb-uclass.c | 8 ++++----
drivers/usb/host/xhci-mem.c | 30 +++++++++++++++---------------
drivers/usb/host/xhci-ring.c | 8 ++++----
drivers/usb/host/xhci.c | 3 +--
4 files changed, 24 insertions(+), 25 deletions(-)
--
2.27.0
next reply other threads:[~2020-07-21 8:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 8:46 Stefan Roese [this message]
2020-07-21 8:46 ` [PATCH v2 1/4] usb: xhci: Add missing endian conversions (cpu_to_leXX / leXX_to_cpu) Stefan Roese
2020-07-21 8:46 ` [PATCH v2 2/4] usb: xhci: xhci_mem_init: Use cpu_to_le64() and not xhci_writeq() Stefan Roese
2020-07-21 8:46 ` [PATCH v2 3/4] usb: usb-uclass.c: Drop le16_to_cpu() as values are already swapped Stefan Roese
2020-07-21 8:46 ` [PATCH v2 4/4] usb: xhci: Add virt_to_phys() to support mapped platforms Stefan Roese
2020-07-30 6:32 ` [PATCH v2 0/4] usb: xhci: Prepare xHCI driver for MIPS Octeon big-endian support Stefan Roese
2020-07-30 6:59 ` Bin Meng
2020-08-05 5:57 ` Stefan Roese
2020-08-05 7:31 ` Marek Vasut
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=20200721084605.3801454-1-sr@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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