public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Christoph Fritz <chf.fritz@googlemail.com>
To: Xavier Drudis Ferran <xdrudis@tinet.cat>
Cc: 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>,  Marek Vasut <marex@denx.de>,
	u-boot@lists.denx.de
Subject: Re: [PATCH v4 0/2] arm: dts: rockchip: rk3399: usb: ehci: Fix EHCI probe in rk3399 to access peripherals by USB 2.
Date: Sun, 19 Feb 2023 20:48:57 +0100	[thread overview]
Message-ID: <ea2ffd447ddaa30bca9bbd0ff86f941ac2ef0ae4.camel@googlemail.com> (raw)
In-Reply-To: <Y5NWmwOWgyd6n4zw@localhost>

Hello Xavier

> The first patch in the series (identical to v3) just registers usb2phy
> as a clock driver (device_bind_driver() didn't work but
> device_bind_driver_to_node() did), without any specific operations, so
> that ehci-generic.c finds it and is happy. It worked in my tests on a
> Rock Pi 4 B+ (rk3399).
> 
> Since Marek Vasut objected to an operationless driver[4], the second
> patch adds enable and disable operations adapted from linux prepare
> and unprepare operations (and round_rate(), which doesn't seem very
> useful anyway since it's a fixed clock). Since there're no users of
> this clock in u-boot, I can't see any difference in my tests with only
> the first patch or both, so I can't be sure it really works if it's
> ever needed, but it's hopefully more complete.
> 

I have tested both of your patches on an rk3399:

without patches applied:

  | starting USB...
  | Bus usb@fe380000: ehci_generic usb@fe380000: Failed to get clocks (ret=-19)
  | Port not available.

with patches applied:

  | starting USB...
  | Bus usb@fe380000: USB EHCI 1.00
  | Bus usb@fe3c0000: USB EHCI 1.00
  | Bus usb@fe800000: Register 2000140 NbrPorts 2


'usb stop' still makes u-boot hang, but with your patches applied
following output gets printed before:

  | => usb stop
  | stopping USB..
  | device_remove: Device 'usb@fe380000' failed to remove, but children are gone
  | device_remove: Device 'usb@fe3c0000' failed to remove, but children are gone
  <u-boot hangs>

Without CONFIG_USB_EHCI_HCD 'usb stop' works just fine.

Thanks
  -- Christoph


  parent reply	other threads:[~2023-02-19 19:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 15:39 [PATCH v4 0/2] arm: dts: rockchip: rk3399: usb: ehci: Fix EHCI probe in rk3399 to access peripherals by USB 2 Xavier Drudis Ferran
2022-12-09 15:44 ` [PATCH v4 1/2] arm: " Xavier Drudis Ferran
2022-12-09 15:47 ` [PATCH v4 2/2] arm: rk3399: usb2phy: phy-rockchip-inno-usb2.c: Implement operations for the 480MHz usb2phy clock in rk3399 Xavier Drudis Ferran
2022-12-11  5:20   ` Marek Vasut
2022-12-11 12:22     ` Xavier Drudis Ferran
2022-12-16  0:43 ` [PATCH v4 0/2] arm: dts: rockchip: rk3399: usb: ehci: Fix EHCI probe in rk3399 to access peripherals by USB 2 Marek Vasut
2023-02-19 19:48 ` Christoph Fritz [this message]
2023-02-27 12:22   ` Xavier Drudis Ferran

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=ea2ffd447ddaa30bca9bbd0ff86f941ac2ef0ae4.camel@googlemail.com \
    --to=chf.fritz@googlemail.com \
    --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 \
    --cc=xdrudis@tinet.cat \
    /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