From: Marek Vasut <marex@denx.de>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Michal Simek <michal.simek@amd.com>,
Sean Anderson <seanga2@gmail.com>, Angus Ainslie <angus@akkea.ca>,
Lukasz Majewski <lukma@denx.de>,
Jan Kiszka <jan.kiszka@siemens.com>,
Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH v4 00/10] usb: dwc3: Refactor dwc3-generic and apply to dwc3-uniphier
Date: Wed, 22 Feb 2023 04:27:54 +0100 [thread overview]
Message-ID: <0bdb96cd-49be-4673-2851-e25fef662584@denx.de> (raw)
In-Reply-To: <57d6fd48-6319-c9cc-901b-76edd5758234@socionext.com>
On 2/22/23 03:00, Kunihiko Hayashi wrote:
> Hi Marek,
>
> On 2023/02/21 0:53, Marek Vasut wrote:
>> On 2/20/23 06:50, Kunihiko Hayashi wrote:
>>> This series achieves refactoring of dwc3-generic.
>>>
>>> First, dwc3-generic allows DT controller nodes to be children of glue
>>> nodes,
>>> but outside of glue nodes.
>>>
>>> To achieve this goal, define a glue-specific function to get controller
>>> node,
>>> look up more reference clocks in the controller node, and initialize
>>> clocks
>>> in children of glue node before access to the controller,
>>>
>>> Next, this series exports the structures and functions from the driver
>>> source
>>> to the header, and replaces dwc3-uniphier driver as one implementation
>>> using
>>> them. This expects dwc3-generic to prevent more SoC-dependent codes.
>>>
>>> The dwc3-uniphier has original USB node, however, tentatively added its
>>> own
>>> node dedicated to U-Boot. After this refactoring, the driver needs to
>>> add
>>> clock entries and PHY driver to enable them corresponding to the
>>> properties
>>> in the original node.
>>>
>>> PATCH 1 has been provided below.
>>>
>>> https://patchwork.ozlabs.org/project/uboot/patch/20221215223822.137739-1-marex@denx.de/
>>>
>>> PATCH 2 is based on the suggested patch from Marek.
>>>
>>> PATCH 4-5 and 9-10 have been already reviewed in the previous v1.
>>> https://lists.denx.de/pipermail/u-boot/2023-January/505689.html
>> I think this series is good to go. Do you want to pull this through the
>> uniphier git tree and send PR to Tom that way , or shall I pick it all
>> via usb git tree ? I think the former option is better.
>
> Currently I don't have the public uniphier git tree and
> the maintainership, so I'd like to choose the latter at the moment.
> Colud you please pick it now?
Applied to usb/next , thanks .
+CC Tom, I think it would be good to get you a git tree for the uniphier
stuff , what do you think ?
next prev parent reply other threads:[~2023-02-22 3:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 5:50 [PATCH v4 00/10] usb: dwc3: Refactor dwc3-generic and apply to dwc3-uniphier Kunihiko Hayashi
2023-02-20 5:50 ` [PATCH v4 01/10] usb: dwc3: Look up reference clock DT phandle in both controller DT nodes Kunihiko Hayashi
2023-02-20 5:50 ` [PATCH v4 02/10] usb: dwc3-generic: Allow different controller DT node pattern Kunihiko Hayashi
2023-02-20 5:50 ` [PATCH v4 03/10] usb: dwc3-generic: Add clock initialization in child DT node Kunihiko Hayashi
2023-02-20 5:50 ` [PATCH v4 04/10] usb: dwc3-generic: Export glue structures and functions Kunihiko Hayashi
2023-02-20 5:50 ` [PATCH v4 05/10] usb: dwc3-generic: Add the size of regs property to glue structure Kunihiko Hayashi
2023-02-20 5:50 ` [PATCH v4 06/10] reset: uniphier: Add USB glue reset support Kunihiko Hayashi
2023-02-20 5:50 ` [PATCH v4 07/10] clk: uniphier: Add missing USB SS-PHY clocks Kunihiko Hayashi
2023-02-20 15:51 ` Marek Vasut
2023-02-20 5:50 ` [PATCH v4 08/10] phy: socionext: Add UniPhier USB3 PHY driver Kunihiko Hayashi
2023-02-20 15:51 ` Marek Vasut
2023-02-20 5:50 ` [PATCH v4 09/10] usb: dwc3-uniphier: Use dwc3-generic instead of xhci-dwc3 Kunihiko Hayashi
2023-02-20 5:50 ` [PATCH v4 10/10] uniphier_defconfig: Disable USB_XHCI_DWC3 Kunihiko Hayashi
2023-02-20 15:53 ` [PATCH v4 00/10] usb: dwc3: Refactor dwc3-generic and apply to dwc3-uniphier Marek Vasut
2023-02-22 2:00 ` Kunihiko Hayashi
2023-02-22 3:27 ` Marek Vasut [this message]
2023-02-22 14:39 ` Tom Rini
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=0bdb96cd-49be-4673-2851-e25fef662584@denx.de \
--to=marex@denx.de \
--cc=angus@akkea.ca \
--cc=hayashi.kunihiko@socionext.com \
--cc=jan.kiszka@siemens.com \
--cc=lukma@denx.de \
--cc=michal.simek@amd.com \
--cc=seanga2@gmail.com \
--cc=trini@konsulko.com \
--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