From: Vinod Koul <vkoul@kernel.org>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: "Mathias Nyman" <mathias.nyman@intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-arm-msm@vger.kernel.org,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
"Christian Lamparter" <chunkeey@googlemail.com>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
"John Stultz" <john.stultz@linaro.org>,
"Alan Stern" <stern@rowland.harvard.edu>,
"Andreas Böhler" <dev@aboehler.at>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v12 2/5] usb: renesas-xhci: Add the renesas xhci driver
Date: Mon, 4 May 2020 20:04:38 +0530 [thread overview]
Message-ID: <20200504143438.GT1375924@vkoul-mobl> (raw)
In-Reply-To: <81e0eff0-8b40-3c47-e39b-929e1dc07fd5@linux.intel.com>
Hi Mathias,
On 04-05-20, 16:01, Mathias Nyman wrote:
> On 30.4.2020 19.59, Vinod Koul wrote:
> > From: Christian Lamparter <chunkeey@googlemail.com>
> >
> > This add a new driver for renesas xhci which is basically a firmware
> > loader for uPD720201 and uPD720202 w/o ROM. The xhci-pci driver will
> > invoke this driver for loading/unloading on relevant devices.
> >
> > This patch adds a firmware loader for the uPD720201K8-711-BAC-A
> > and uPD720202K8-711-BAA-A variant. Both of these chips are listed
> > in Renesas' R19UH0078EJ0500 Rev.5.00 "User's Manual: Hardware" as
> > devices which need the firmware loader on page 2 in order to
> > work as they "do not support the External ROM".
> >
> > The "Firmware Download Sequence" is describe in chapter
> > "7.1 FW Download Interface" R19UH0078EJ0500 Rev.5.00 page 131.
> >
> > The firmware "K2013080.mem" is available from a USB3.0 Host to
> > PCIe Adapter (PP2U-E card) "Firmware download" archive. An
> > alternative version can be sourced from Netgear's WNDR4700 GPL
> > archives.
> >
> > The release notes of the PP2U-E's "Firmware Download" ver 2.0.1.3
> > (2012-06-15) state that the firmware is for the following devices:
> > - uPD720201 ES 2.0 sample whose revision ID is 2.
> > - uPD720201 ES 2.1 sample & CS sample & Mass product, ID is 3.
> > - uPD720202 ES 2.0 sample & CS sample & Mass product, ID is 2.
> >
> > Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
> > Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> > [vkoul: fixed comments:
> > used macros for timeout count and delay
> > removed renesas_fw_alive_check
> > cleaned renesas_fw_callback
> > removed recursion for renesas_fw_download
> > add register defines and field names
> > move to a separate file
> > make fw loader as sync probe so that we execute in probe and
> > prevent race
> > export symbols for xhci-pci to use]
> > Signed-off-by: Vinod Koul <vkoul@kernel.org>
> > ---
> > drivers/usb/host/Makefile | 2 +-
> > drivers/usb/host/xhci-pci-renesas.c | 365 ++++++++++++++++++++++++++++
> > drivers/usb/host/xhci-pci.h | 16 ++
> > 3 files changed, 382 insertions(+), 1 deletion(-)
> > create mode 100644 drivers/usb/host/xhci-pci-renesas.c
> > create mode 100644 drivers/usb/host/xhci-pci.h
> >
> > diff --git a/drivers/usb/host/Makefile b/drivers/usb/host/Makefile
> > index b191361257cc..f3a5a2f01874 100644
> > --- a/drivers/usb/host/Makefile
> > +++ b/drivers/usb/host/Makefile
> > @@ -70,7 +70,7 @@ obj-$(CONFIG_USB_OHCI_HCD_DAVINCI) += ohci-da8xx.o
> > obj-$(CONFIG_USB_UHCI_HCD) += uhci-hcd.o
> > obj-$(CONFIG_USB_FHCI_HCD) += fhci.o
> > obj-$(CONFIG_USB_XHCI_HCD) += xhci-hcd.o
> > -obj-$(CONFIG_USB_XHCI_PCI) += xhci-pci.o
> > +obj-$(CONFIG_USB_XHCI_PCI) += xhci-pci.o xhci-pci-renesas.o
>
> Hmm, now we end up with two modules, xhci-pci and xhci-pci-renesas, even if
> xhci-pci-renesas just includes helper functions to load firmware for renesas.
Right, these are two modules. Do you forsee an issue with two ko's
>
> My kbuild knowledge is limited, but one way to solve this would be to
> rename xhci-pci.c to xhci-pci-core.c and add:
Yeah i wanted to avoid the rename (stopped short of suggesting that)..
>
> xhci-pci-y := xhci-pci-core.o xhci-pci-renesas.o
>
> unless someone can suggest a better way to solve this
I dont have any better idea atm!
So if you are okay with rename of file, I can do that first and then
these patches
Thanks
--
~Vinod
next prev parent reply other threads:[~2020-05-04 14:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 16:59 [PATCH v12 0/5] usb: xhci: Add support for Renesas USB controllers Vinod Koul
2020-04-30 16:59 ` [PATCH v12 1/5] usb: hci: add hc_driver as argument for usb_hcd_pci_probe Vinod Koul
2020-04-30 16:59 ` [PATCH v12 2/5] usb: renesas-xhci: Add the renesas xhci driver Vinod Koul
2020-05-04 13:01 ` Mathias Nyman
2020-05-04 14:34 ` Vinod Koul [this message]
2020-05-05 11:04 ` Greg Kroah-Hartman
2020-05-05 11:33 ` Vinod Koul
2020-05-05 12:05 ` Greg Kroah-Hartman
2020-04-30 16:59 ` [PATCH v12 3/5] usb: xhci: Add support for Renesas controller with memory Vinod Koul
2020-04-30 16:59 ` [PATCH v12 4/5] usb: renesas-xhci: Add ROM loader for uPD720201 Vinod Koul
2020-04-30 16:59 ` [PATCH v12 5/5] usb: xhci: provide a debugfs hook for erasing rom 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=20200504143438.GT1375924@vkoul-mobl \
--to=vkoul@kernel.org \
--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-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=mathias.nyman@linux.intel.com \
--cc=stern@rowland.harvard.edu \
--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
all inboxes | Powered by JetHome®