linux-kernel - Re: [RFC PATCH v1 0/6] rockchip: add a functional usb3 phy driver for rk3328

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <3536B507-8658-4377-A1AC-2C5D9093BDEB@gmail.com>
Date: Wed, 15 Jan 2025 14:25:26 +0100
From: Piotr Oniszczuk <piotr.oniszczuk@...il.com>
To: Peter Geis <pgwipeout@...il.com>
Cc: Heiko Stuebner <heiko@...ech.de>,
 Algea Cao <algea.cao@...k-chips.com>,
 Michael Turquette <mturquette@...libre.com>,
 kever.yang@...k-chips.com,
 linux-phy@...ts.infradead.org,
 wulf@...k-chips.com,
 zyw@...k-chips.com,
 Dragan Simic <dsimic@...jaro.org>,
 Kishon Vijay Abraham I <kishon@...nel.org>,
 Rob Herring <robh@...nel.org>,
 Sebastian Reichel <sebastian.reichel@...labora.com>,
 linux-clk@...r.kernel.org,
 linux-rockchip@...ts.infradead.org,
 devicetree@...r.kernel.org,
 Conor Dooley <conor+dt@...nel.org>,
 Philipp Zabel <p.zabel@...gutronix.de>,
 Arnd Bergmann <arnd@...db.de>,
 Jonas Karlman <jonas@...boo.se>,
 frank.wang@...k-chips.com,
 Elaine Zhang <zhangqing@...k-chips.com>,
 Alex Bee <knaerzche@...il.com>,
 william.wu@...k-chips.com,
 Zhang Yubing <yubing.zhang@...k-chips.com>,
 Johan Jonker <jbx6244@...il.com>,
 linux-arm-kernel@...ts.infradead.org,
 Trevor Woerner <twoerner@...il.com>,
 Stephen Boyd <sboyd@...nel.org>,
 linux-kernel@...r.kernel.org,
 Vinod Koul <vkoul@...nel.org>,
 FUKAUMI Naoki <naoki@...xa.com>,
 Diederik de Haas <didi.debian@...ow.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>
Subject: Re: [RFC PATCH v1 0/6] rockchip: add a functional usb3 phy driver for
 rk3328



> Wiadomość napisana przez Peter Geis <pgwipeout@...il.com> w dniu 15 sty 2025, o godz. 14:15:
> 
>> 
>> 
>> pls find:
>> 
>> dtsi: https://gist.github.com/warpme/6af9e2778fb06bfb47b64f98fe79d678
>> and dt: https://gist.github.com/warpme/79340c54c87b2b1e52f2a146461d8c9f
>> 
>> 
>> and compiled .dtb
> 
> It all looks good.
> Do you have any CRU errors in the boot log?
> Can you check for the presence of clk_ref_usb3otg in
> /sys/kernel/debug/clk/clk_summary?
> 
>> 

cru errors in dmesg - seems no any.
here is my dmesg: https://gist.github.com/warpme/ecf38482cc88fb68471355d011ecf974

For clk_ref_usb3otg i’m getting following:

root@...h-frontend-e67a8de4c815:~ # cat /sys/kernel/debug/clk/clk_summary | grep usb3
    clk_usb3otg_suspend              0       0        0        30770       0          0     50000      N      deviceless                      no_connection_id
    clk_usb3otg_ref                  0       0        0        24000000    0          0     50000      N      deviceless                      no_connection_id
    clk_ref_usb3otg                  0       0        0        24000000    0          0     50000      Y      deviceless                      no_connection_id
                   pclk_usb3_grf     0       0        0        75000000    0          0     50000      Y                     deviceless                      no_connection_id
                   pclk_usb3phy_pipe 0       0        0        75000000    0          0     50000      N                     deviceless                      no_connection_id
                   pclk_usb3phy_otg  0       0        0        75000000    0          0     50000      N                     deviceless                      no_connection_id
          clk_ref_usb3otg_src        0       0        0        37500000    0          0     50000      N            deviceless                      no_connection_id
                   aclk_usb3otg      0       0        0        150000000   0          0     50000      N                     deviceless                      no_connection_id