From: Heiko Stuebner <heiko@sntech.de>
To: Dan Johansen <strit@manjaro.org>,
Frank Wunderlich <frank-w@public-files.de>
Cc: Frank Wunderlich <linux@fw-web.de>,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Peter Geis <pgwipeout@gmail.com>,
Michael Riesch <michael.riesch@wolfvision.net>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Aw: Re: Re: [PATCH] arm64: dts: rockchip: Fix clocks for rk356x usb
Date: Sat, 09 Apr 2022 13:01:25 +0200 [thread overview]
Message-ID: <4559790.iIbC2pHGDl@phil> (raw)
In-Reply-To: <trinity-b6d141b2-264a-4a57-9707-6a38a80cea16-1649501859874@3c-app-gmx-bap35>
Am Samstag, 9. April 2022, 12:57:39 CEST schrieb Frank Wunderlich:
> Hi
> > Gesendet: Samstag, 09. April 2022 um 12:40 Uhr
> > Von: "Dan Johansen" <strit@manjaro.org>
>
> > So the issue is only with usb 3 ports, not usb 2 ports?
>
> my board has no standalone usb2-ports. usb2 is integrated into the usb3 ports (dual phy). here both were not working.
>
> afaik rk3566 has standalone usb2 ports that may not be broken, but i have no such board for testing.
As far as I understand the issue now after checking the code, this
patch actually fixes the usb3 series from Peter, right?
I.e. the usb-nodes that are fixed in this patch are not yet present
in the main rk356x dtsi and only get added in
"arm64: dts: rockchip: add rk356x dwc3 usb3 nodes" [0]
As we don't want to add broken changes, this fix should squashed
into a next version of the patch adding the nodes.
Heiko
[0] https://lore.kernel.org/r/20220408151237.3165046-4-pgwipeout@gmail.com
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Dan Johansen <strit@manjaro.org>,
Frank Wunderlich <frank-w@public-files.de>
Cc: Frank Wunderlich <linux@fw-web.de>,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Peter Geis <pgwipeout@gmail.com>,
Michael Riesch <michael.riesch@wolfvision.net>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Aw: Re: Re: [PATCH] arm64: dts: rockchip: Fix clocks for rk356x usb
Date: Sat, 09 Apr 2022 13:01:25 +0200 [thread overview]
Message-ID: <4559790.iIbC2pHGDl@phil> (raw)
In-Reply-To: <trinity-b6d141b2-264a-4a57-9707-6a38a80cea16-1649501859874@3c-app-gmx-bap35>
Am Samstag, 9. April 2022, 12:57:39 CEST schrieb Frank Wunderlich:
> Hi
> > Gesendet: Samstag, 09. April 2022 um 12:40 Uhr
> > Von: "Dan Johansen" <strit@manjaro.org>
>
> > So the issue is only with usb 3 ports, not usb 2 ports?
>
> my board has no standalone usb2-ports. usb2 is integrated into the usb3 ports (dual phy). here both were not working.
>
> afaik rk3566 has standalone usb2 ports that may not be broken, but i have no such board for testing.
As far as I understand the issue now after checking the code, this
patch actually fixes the usb3 series from Peter, right?
I.e. the usb-nodes that are fixed in this patch are not yet present
in the main rk356x dtsi and only get added in
"arm64: dts: rockchip: add rk356x dwc3 usb3 nodes" [0]
As we don't want to add broken changes, this fix should squashed
into a next version of the patch adding the nodes.
Heiko
[0] https://lore.kernel.org/r/20220408151237.3165046-4-pgwipeout@gmail.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Dan Johansen <strit@manjaro.org>,
Frank Wunderlich <frank-w@public-files.de>
Cc: Frank Wunderlich <linux@fw-web.de>,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Peter Geis <pgwipeout@gmail.com>,
Michael Riesch <michael.riesch@wolfvision.net>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Aw: Re: Re: [PATCH] arm64: dts: rockchip: Fix clocks for rk356x usb
Date: Sat, 09 Apr 2022 13:01:25 +0200 [thread overview]
Message-ID: <4559790.iIbC2pHGDl@phil> (raw)
In-Reply-To: <trinity-b6d141b2-264a-4a57-9707-6a38a80cea16-1649501859874@3c-app-gmx-bap35>
Am Samstag, 9. April 2022, 12:57:39 CEST schrieb Frank Wunderlich:
> Hi
> > Gesendet: Samstag, 09. April 2022 um 12:40 Uhr
> > Von: "Dan Johansen" <strit@manjaro.org>
>
> > So the issue is only with usb 3 ports, not usb 2 ports?
>
> my board has no standalone usb2-ports. usb2 is integrated into the usb3 ports (dual phy). here both were not working.
>
> afaik rk3566 has standalone usb2 ports that may not be broken, but i have no such board for testing.
As far as I understand the issue now after checking the code, this
patch actually fixes the usb3 series from Peter, right?
I.e. the usb-nodes that are fixed in this patch are not yet present
in the main rk356x dtsi and only get added in
"arm64: dts: rockchip: add rk356x dwc3 usb3 nodes" [0]
As we don't want to add broken changes, this fix should squashed
into a next version of the patch adding the nodes.
Heiko
[0] https://lore.kernel.org/r/20220408151237.3165046-4-pgwipeout@gmail.com
next prev parent reply other threads:[~2022-04-09 11:01 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 7:51 [PATCH] arm64: dts: rockchip: Fix clocks for rk356x usb Frank Wunderlich
2022-04-09 7:51 ` Frank Wunderlich
2022-04-09 7:51 ` Frank Wunderlich
2022-04-09 10:14 ` Aw: " Frank Wunderlich
2022-04-09 10:14 ` Frank Wunderlich
2022-04-09 10:14 ` Frank Wunderlich
2022-04-09 10:23 ` Heiko Stuebner
2022-04-09 10:23 ` Heiko Stuebner
2022-04-09 10:23 ` Heiko Stuebner
2022-04-09 10:32 ` Aw: " Frank Wunderlich
2022-04-09 10:32 ` Frank Wunderlich
2022-04-09 10:32 ` Frank Wunderlich
2022-04-09 10:40 ` Dan Johansen
2022-04-09 10:40 ` Dan Johansen
2022-04-09 10:40 ` Dan Johansen
2022-04-09 10:57 ` Aw: " Frank Wunderlich
2022-04-09 10:57 ` Frank Wunderlich
2022-04-09 10:57 ` Frank Wunderlich
2022-04-09 11:01 ` Heiko Stuebner [this message]
2022-04-09 11:01 ` Heiko Stuebner
2022-04-09 11:01 ` Heiko Stuebner
2022-04-09 11:13 ` Aw: " Frank Wunderlich
2022-04-09 11:13 ` Frank Wunderlich
2022-04-09 11:13 ` Frank Wunderlich
2022-04-09 11:14 ` Aw: " Peter Geis
2022-04-09 11:14 ` Peter Geis
2022-04-09 11:14 ` Peter Geis
2022-04-09 11:30 ` Peter Geis
2022-04-09 11:30 ` Peter Geis
2022-04-09 11:30 ` Peter Geis
2022-04-09 11:35 ` Heiko Stuebner
2022-04-09 11:35 ` Heiko Stuebner
2022-04-09 11:35 ` Heiko Stuebner
2022-04-09 11:51 ` Peter Geis
2022-04-09 11:51 ` Peter Geis
2022-04-09 11:51 ` Peter Geis
2022-04-09 11:56 ` Aw: " Frank Wunderlich
2022-04-09 11:56 ` Frank Wunderlich
2022-04-09 11:56 ` Frank Wunderlich
2022-04-09 15:26 ` Peter Geis
2022-04-09 15:26 ` Peter Geis
2022-04-09 15:26 ` Peter Geis
2022-04-10 16:53 ` Heiko Stuebner
2022-04-10 16:53 ` Heiko Stuebner
2022-04-10 16:53 ` Heiko Stuebner
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=4559790.iIbC2pHGDl@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@fw-web.de \
--cc=michael.riesch@wolfvision.net \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=strit@manjaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.