From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: MR <m.reichl@fivetechno.de>
Cc: linux-rockchip@lists.infradead.org,
Robin Murphy <robin.murphy@arm.com>,
heiko@sntech.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: rk3399-roc-pc does not boot
Date: Fri, 17 Jun 2022 13:47:05 +0200 [thread overview]
Message-ID: <YqxpuT36/sjQKm0o@Red> (raw)
In-Reply-To: <9CC86176-19B0-491F-86A4-F95E670B0A66@fivetechno.de>
Le Fri, Jun 17, 2022 at 01:43:05PM +0200, MR a écrit :
>
>
> Am 17. Juni 2022 11:58:03 MESZ schrieb Robin Murphy <robin.murphy@arm.com>:
> >On 2022-06-17 10:06, Corentin Labbe wrote:
> >> Hello
> >>
> >> I try to add rk3399-roc-pc to kernelCI but this board fail to ends its boot with any kernel I try.
> >> It boot normally up to starting init but it stucks shorty after.
> >> It fail on 5.10, 5.15, 5.17, 5.18 and linux-next.
> >> When disabling CONFIG_USB, the board boots successfully.
> >>
> >> In dmesg I see OF: graph: no port node found in /i2c@ff160000/usb-typec@22
> >> According to Documentation/devicetree/bindings/usb/fcs,fusb302.txt, the port is mandatory.
> >> Can it be possible that the problem was that the power port being disabled ?
> >
> >Indeed, I believe the OF graph error is just a meaningless annoyance, but the general problem sounds like it's probably the same thing that's come up before:
> >
> >https://lore.kernel.org/all/0ac6bbe7-6395-526d-213c-ac58a19d8673@fivetechno.de/
> >
> >Disabling CONFIG_TYPEC_FUSB302 or blacklisting the fusb302 module should help confirm that. I have no idea if it's still an open problem, or if it's been fixed and you might just need to define the proper power role in the DT; this just triggered a memory of that older thread :)
> >
> >Robin.
>
> Yes, the issue above is still there. I therefore use dumb 5 V, 4 A USB power supplies that do not react on the USB-C communication.
>
> Markus
@Markus
Could you try the diff I just send ?
Thanks
_______________________________________________
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: Corentin Labbe <clabbe.montjoie@gmail.com>
To: MR <m.reichl@fivetechno.de>
Cc: linux-rockchip@lists.infradead.org,
Robin Murphy <robin.murphy@arm.com>,
heiko@sntech.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: rk3399-roc-pc does not boot
Date: Fri, 17 Jun 2022 13:47:05 +0200 [thread overview]
Message-ID: <YqxpuT36/sjQKm0o@Red> (raw)
In-Reply-To: <9CC86176-19B0-491F-86A4-F95E670B0A66@fivetechno.de>
Le Fri, Jun 17, 2022 at 01:43:05PM +0200, MR a écrit :
>
>
> Am 17. Juni 2022 11:58:03 MESZ schrieb Robin Murphy <robin.murphy@arm.com>:
> >On 2022-06-17 10:06, Corentin Labbe wrote:
> >> Hello
> >>
> >> I try to add rk3399-roc-pc to kernelCI but this board fail to ends its boot with any kernel I try.
> >> It boot normally up to starting init but it stucks shorty after.
> >> It fail on 5.10, 5.15, 5.17, 5.18 and linux-next.
> >> When disabling CONFIG_USB, the board boots successfully.
> >>
> >> In dmesg I see OF: graph: no port node found in /i2c@ff160000/usb-typec@22
> >> According to Documentation/devicetree/bindings/usb/fcs,fusb302.txt, the port is mandatory.
> >> Can it be possible that the problem was that the power port being disabled ?
> >
> >Indeed, I believe the OF graph error is just a meaningless annoyance, but the general problem sounds like it's probably the same thing that's come up before:
> >
> >https://lore.kernel.org/all/0ac6bbe7-6395-526d-213c-ac58a19d8673@fivetechno.de/
> >
> >Disabling CONFIG_TYPEC_FUSB302 or blacklisting the fusb302 module should help confirm that. I have no idea if it's still an open problem, or if it's been fixed and you might just need to define the proper power role in the DT; this just triggered a memory of that older thread :)
> >
> >Robin.
>
> Yes, the issue above is still there. I therefore use dumb 5 V, 4 A USB power supplies that do not react on the USB-C communication.
>
> Markus
@Markus
Could you try the diff I just send ?
Thanks
_______________________________________________
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: Corentin Labbe <clabbe.montjoie@gmail.com>
To: MR <m.reichl@fivetechno.de>
Cc: linux-rockchip@lists.infradead.org,
Robin Murphy <robin.murphy@arm.com>,
heiko@sntech.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: rk3399-roc-pc does not boot
Date: Fri, 17 Jun 2022 13:47:05 +0200 [thread overview]
Message-ID: <YqxpuT36/sjQKm0o@Red> (raw)
In-Reply-To: <9CC86176-19B0-491F-86A4-F95E670B0A66@fivetechno.de>
Le Fri, Jun 17, 2022 at 01:43:05PM +0200, MR a écrit :
>
>
> Am 17. Juni 2022 11:58:03 MESZ schrieb Robin Murphy <robin.murphy@arm.com>:
> >On 2022-06-17 10:06, Corentin Labbe wrote:
> >> Hello
> >>
> >> I try to add rk3399-roc-pc to kernelCI but this board fail to ends its boot with any kernel I try.
> >> It boot normally up to starting init but it stucks shorty after.
> >> It fail on 5.10, 5.15, 5.17, 5.18 and linux-next.
> >> When disabling CONFIG_USB, the board boots successfully.
> >>
> >> In dmesg I see OF: graph: no port node found in /i2c@ff160000/usb-typec@22
> >> According to Documentation/devicetree/bindings/usb/fcs,fusb302.txt, the port is mandatory.
> >> Can it be possible that the problem was that the power port being disabled ?
> >
> >Indeed, I believe the OF graph error is just a meaningless annoyance, but the general problem sounds like it's probably the same thing that's come up before:
> >
> >https://lore.kernel.org/all/0ac6bbe7-6395-526d-213c-ac58a19d8673@fivetechno.de/
> >
> >Disabling CONFIG_TYPEC_FUSB302 or blacklisting the fusb302 module should help confirm that. I have no idea if it's still an open problem, or if it's been fixed and you might just need to define the proper power role in the DT; this just triggered a memory of that older thread :)
> >
> >Robin.
>
> Yes, the issue above is still there. I therefore use dumb 5 V, 4 A USB power supplies that do not react on the USB-C communication.
>
> Markus
@Markus
Could you try the diff I just send ?
Thanks
next prev parent reply other threads:[~2022-06-17 11:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 9:06 rk3399-roc-pc does not boot Corentin Labbe
2022-06-17 9:06 ` Corentin Labbe
2022-06-17 9:06 ` Corentin Labbe
2022-06-17 9:58 ` Robin Murphy
2022-06-17 9:58 ` Robin Murphy
2022-06-17 9:58 ` Robin Murphy
2022-06-17 11:35 ` Corentin Labbe
2022-06-17 11:35 ` Corentin Labbe
2022-06-17 11:35 ` Corentin Labbe
2022-06-17 11:48 ` MR
2022-06-17 11:48 ` MR
2022-06-17 11:48 ` MR
2022-06-17 11:43 ` MR
2022-06-17 11:43 ` MR
2022-06-17 11:43 ` MR
2022-06-17 11:47 ` Corentin Labbe [this message]
2022-06-17 11:47 ` Corentin Labbe
2022-06-17 11:47 ` Corentin Labbe
2022-06-17 11:50 ` MR
2022-06-17 11:50 ` MR
2022-06-17 11:50 ` MR
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=YqxpuT36/sjQKm0o@Red \
--to=clabbe.montjoie@gmail.com \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=m.reichl@fivetechno.de \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
/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.