From: Vinod Koul <vkoul@kernel.org>
To: 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>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/4] usb: xhci: Add support for Renesas USB controllers
Date: Thu, 21 Nov 2019 10:24:57 +0530 [thread overview]
Message-ID: <20191121045457.GH82508@vkoul-mobl> (raw)
In-Reply-To: <20191106083843.1718437-1-vkoul@kernel.org>
On 06-11-19, 14:08, 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 two patches from Christian which supported these controllers
> w/o ROM and later my patches for ROM support and multiple firmware versions.
Greg, Mathias
Any feedback on this?
>
> 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 firware 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 multiple fw order
>
> Christian Lamparter (1):
> usb: xhci: add firmware loader for uPD720201 and uPD720202 w/o ROM
>
> Vinod Koul (3):
> usb: xhci: Add ROM loader for uPD720201
> usb: xhci: allow multiple firmware versions
> usb: xhci: provide a debugfs hook for erasing rom
>
> drivers/usb/host/xhci-pci.c | 911 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 911 insertions(+)
>
> --
> 2.23.0
--
~Vinod
next prev parent reply other threads:[~2019-11-21 4:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 8:38 [PATCH v5 0/4] usb: xhci: Add support for Renesas USB controllers Vinod Koul
2019-11-06 8:38 ` [PATCH v5 1/4] usb: xhci: add firmware loader for uPD720201 and uPD720202 w/o ROM Vinod Koul
2019-11-06 8:38 ` [PATCH v5 2/4] usb: xhci: Add ROM loader for uPD720201 Vinod Koul
2019-11-06 8:38 ` [PATCH v5 3/4] usb: xhci: allow multiple firmware versions Vinod Koul
2019-11-06 8:38 ` [PATCH v5 4/4] usb: xhci: provide a debugfs hook for erasing rom Vinod Koul
2019-11-21 4:54 ` Vinod Koul [this message]
2019-11-26 15:59 ` [PATCH v5 0/4] usb: xhci: Add support for Renesas USB controllers Mathias Nyman
2019-12-06 4:21 ` Vinod Koul
2020-01-07 19:51 ` John Stultz
2020-01-08 4:07 ` Vinod Koul
2020-01-08 6:24 ` Greg Kroah-Hartman
2020-01-08 16:00 ` Mathias Nyman
2020-01-08 18:29 ` Greg Kroah-Hartman
2020-01-09 12:09 ` Vinod Koul
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=20191121045457.GH82508@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=chunkeey@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).