From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Vinod Koul <vkoul@kernel.org>,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-arm-msm@vger.kernel.org,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
"Christian Lamparter" <chunkeey@googlemail.com>,
"John Stultz" <john.stultz@linaro.org>,
"Alan Stern" <stern@rowland.harvard.edu>,
"Andreas Böhler" <dev@aboehler.at>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH REPOST v13 0/4] usb: xhci: Add support for Renesas USB controllers
Date: Thu, 14 May 2020 17:14:31 +0300 [thread overview]
Message-ID: <4ff01657-c844-d52a-0b42-81a50327a5f8@linux.intel.com> (raw)
In-Reply-To: <20200514122039.300417-1-vkoul@kernel.org>
On 14.5.2020 15.20, Vinod Koul wrote:
> This series add support for Renesas USB controllers uPD720201 and uPD720202.
> These require firmware to be loaded and in case devices have ROM those can
> also be programmed if empty. If ROM is programmed, it runs from ROM as well.
>
> This includes patches from Christian which supported these controllers w/o
> ROM and later my patches for ROM support and debugfs hook for rom erase and
> export of xhci-pci functions.
>
> Changes in v13-repost:
> - drop debugfs patch 5 and repost
>
> Changes in v13:
> - Make rensesas as independent module invoke by xhci-pci which can be
> selected by users of such hardware
>
> Changes in v12:
> - Restore back module name for xhci-pci, so now renesas is a separate
> module, export init/exit routines from renesas modules
> - Update changelog on patch2
>
> Changes in v11:
> - update xhci->quirks and use that in remove function
> - remove error return renesas_verify_fw_version()
> - remove renesas_download_rom() and modify renesas_fw_download_image() for
> reuse
> Changes in v10:
> remove renesas_xhci_pci_probe and call renesas_xhci_check_request_fw and
> also cleanup exit code along with it.
>
> Changes in v9:
> Make fw load a sync call and have single instance of probe execute,
> elimating probe/remove races
> Add quirk for renesas and use that for loading
>
> Changes in v8:
> Fix compile error reported by Kbuild-bot by making usb_hcd_pci_probe() take
> const struct hc_driver * as argument
>
> Changes in v7:
> Make a single module which removes issues with module loading
> Keep the renesas code in renesas file
> Add hc_driver as argument for usb_hcd_pci_probe and modify hdc drivers to
> pass this and not use driver_data
> Use driver data for fw name
> Remove code to check if we need to load firmware or not
> remove multiple fw version support, we can do that with symlink in
> userspace
>
> Changes in v6:
> Move the renesas code into a separate driver which invokes xhci-pci functions.
>
> Changes in v5:
> Added a debugfs rom erase patch, helps in debugging
> Squashed patch 1 & 2 as requested by Mathias
>
> Changes in v4:
> Rollback the delay values as we got device failures
>
> Changes in v3:
> Dropped patch 2 as discussed with Christian
> Removed aligned 8 bytes check
> Change order for firmware search from highest version to lowest
> Added entry for new firmware for device 0x14 as well
> Add tested by Christian
>
> Changes in v2:
> used macros for timeout count and delay
> removed renesas_fw_alive_check
> cleaned renesas_fw_callback
> removed recurion for renesas_fw_download
> added MODULE_FIRMWARE
> added comment for multip
>
> Christian Lamparter (1):
> usb: renesas-xhci: Add the renesas xhci driver
>
> Vinod Koul (3):
> usb: hci: add hc_driver as argument for usb_hcd_pci_probe
> usb: xhci: Add support for Renesas controller with memory
> usb: renesas-xhci: Add ROM loader for uPD720201
>
> drivers/usb/core/hcd-pci.c | 7 +-
> drivers/usb/host/Kconfig | 9 +
> drivers/usb/host/Makefile | 1 +
> drivers/usb/host/ehci-pci.c | 6 +-
> drivers/usb/host/ohci-pci.c | 9 +-
> drivers/usb/host/uhci-pci.c | 8 +-
> drivers/usb/host/xhci-pci-renesas.c | 645 ++++++++++++++++++++++++++++
> drivers/usb/host/xhci-pci.c | 47 +-
> drivers/usb/host/xhci-pci.h | 28 ++
> drivers/usb/host/xhci.h | 1 +
> include/linux/usb/hcd.h | 3 +-
> 11 files changed, 742 insertions(+), 22 deletions(-)
> create mode 100644 drivers/usb/host/xhci-pci-renesas.c
> create mode 100644 drivers/usb/host/xhci-pci.h
>
For all 4 patches:
Acked-by: Mathias Nyman <mathias.nyman@linux.intel.com>
prev parent reply other threads:[~2020-05-14 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 12:20 [PATCH REPOST v13 0/4] usb: xhci: Add support for Renesas USB controllers Vinod Koul
2020-05-14 12:20 ` [PATCH REPOST v13 1/4] usb: hci: add hc_driver as argument for usb_hcd_pci_probe Vinod Koul
2020-05-14 12:20 ` [PATCH REPOST v13 2/4] usb: renesas-xhci: Add the renesas xhci driver Vinod Koul
2020-05-14 12:20 ` [PATCH REPOST v13 3/4] usb: xhci: Add support for Renesas controller with memory Vinod Koul
2020-05-14 12:20 ` [PATCH REPOST v13 4/4] usb: renesas-xhci: Add ROM loader for uPD720201 Vinod Koul
2020-05-14 14:14 ` Mathias Nyman [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=4ff01657-c844-d52a-0b42-81a50327a5f8@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=chunkeey@googlemail.com \
--cc=dev@aboehler.at \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=stern@rowland.harvard.edu \
--cc=vkoul@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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