From: Xavier Drudis Ferran <xdrudis@tinet.cat>
To: Marek Vasut <marex@denx.de>
Cc: Xavier Drudis Ferran <xdrudis@tinet.cat>,
u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Kever Yang <kever.yang@rock-chips.com>,
Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>
Subject: Re: [PATCH v2] arm: dts: rockchip: rk3399: usb: ehci: Fix EHCI probe in rk3399 to access peripherals by USB 2.
Date: Tue, 6 Dec 2022 19:45:08 +0100 [thread overview]
Message-ID: <Y4+NtLfo6RvXzbTN@localhost> (raw)
In-Reply-To: <1d03c21b-19f9-dfb2-9560-848ccaeef425@denx.de>
El Mon, Dec 05, 2022 at 08:08:40PM +0100, Marek Vasut deia:
> On 12/5/22 19:54, Xavier Drudis Ferran wrote:
> > 5- Trying to replicate linux and have usb2phy somehow provide a clk,
> > or have a separate clock device for usb2phy in addition to the phy
> > device. I just can't seem to imagine how to achieve this with the
> > U-Boot driver model, maybe because of my limited familiarity with
> > it.
>
> Yes please
>
> Have a look at the end of drivers/led/led_gpio.c and how gpio_led_wrap binds
> a gpio_led driver to each LED. You can bind an UCLASS_PHY and UCLASS_CLK
> driver to the u2phy0 the same way, the u2phy0 would behave the same way as
> gpio_led_wrap wrapper . You would likely be using device_bind_driver()
> instead of device_bind_driver_to_node() in the bind callback.
>
Ok, I will take a look and send a v3 if I understand it.
Thank you.
prev parent reply other threads:[~2022-12-06 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 18:54 [PATCH v2] arm: dts: rockchip: rk3399: usb: ehci: Fix EHCI probe in rk3399 to access peripherals by USB 2 Xavier Drudis Ferran
2022-12-05 19:08 ` Marek Vasut
2022-12-06 18:45 ` Xavier Drudis Ferran [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=Y4+NtLfo6RvXzbTN@localhost \
--to=xdrudis@tinet.cat \
--cc=kever.yang@rock-chips.com \
--cc=lukma@denx.de \
--cc=marex@denx.de \
--cc=philipp.tomsich@vrull.eu \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--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